> For the complete documentation index, see [llms.txt](https://docs.guardianservice.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardianservice.app/technical-information/users/standard-registry-users-schemas-and-policies/policies/tools.md).

# Tools

**Overview of Tools in the Guardian**

In the Guardian, 'Tools' are integral components within the policy architecture, offering specialized functionalities distinct from other policy elements. These Tools are designed to align with digital methodologies used by organizations like UNFCCC and Verra, thus ensuring standardization and effectiveness in policy execution.

**Defining Characteristics of Tools**

1. **Component-Based Structure:** Unlike Modules, Tools maintain a component-based structure within policies. They are linked to policies through references rather than being fully embedded, maintaining a level of isolation. This design preserves the integrity of their internal mechanics, such as blocks, events, and schemas.
2. **Interface-Driven Interoperability:** Tools are equipped with dedicated interfaces for seamless interaction within the policy ecosystem. These interfaces facilitate effective communication and functionality of Tools alongside other policy content.
3. **Limited Editability:** Tools are designed with restricted editability to maintain their standardized functions. Standard Registries can modify only the external interfaces of Tools, ensuring consistent application and performance in line with established methodologies.
4. **Hierarchical Integration:** Unique to Tools is their ability to encapsulate other Tools, allowing for a hierarchical structure within policies. This feature enables the development of complex, layered policy frameworks where each Tool contributes specific capabilities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guardianservice.app/technical-information/users/standard-registry-users-schemas-and-policies/policies/tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.