get_docFetch one public Cleotic documentation page by slug. Links inside a page are slugs this tool takes. Use search_docs first when you have no slug.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Documentation slug from search_docs, for example core-concepts/visibility-metrics. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| generated_at | Yes | RFC 3339 time the response was made. | |
| schema_version | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / slug / descriptionPrevious value: -"Documentation slug from search_docs, for example analytics/share-of-voice."New value: +"Documentation slug from search_docs, for example core-concepts/visibility-metrics."Input schema / additionalPropertiesAdded value: +falseInput schema / properties / slug / descriptionPrevious value: -"Documentation slug, for example analytics/share-of-voice."New value: +"Documentation slug from search_docs, for example analytics/share-of-voice."Input schema / properties / slug / minLengthAdded value: +1Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "content": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "title",
+ "url"
+ ],
+ "type": "object"
+ },
+ "generated_at": {
+ "description": "RFC 3339 time the response was made.",
+ "type": "string"
+ },
+ "schema_version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "schema_version",
+ "generated_at",
+ "data"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the 'public' scope constraint, which is useful (private pages presumably fail) but there is no error behavior, rate limit, or failure-mode context beyond that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, no filler, with the core action front-loaded and the routing hint last. Every sentence carries distinct information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, read-only lookup with an output schema and full annotation coverage, the description supplies everything needed: what is fetched, what the slug is, and how to obtain one. Return values are properly left to the output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the slug parameter is already documented with an example, so the baseline would be 3. The description adds real value by explaining where slugs come from (in-page links, or search_docs output), which clarifies the value the agent should pass.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource with scope: fetch one public Cleotic documentation page by slug. The 'public' qualifier and 'by slug' key distinguish it cleanly from list_pages and search_docs without needing to open either schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: 'Use search_docs first when you have no slug' names the alternative sibling and the exact condition that selects it. It also clarifies that in-page links are already valid slugs, telling the agent when no lookup step is needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.