get_guideGet one guide's registry row by slug, with its artifact + routing-surface status.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The guide slug, e.g. start-a-company. |
| Name | Required | Description | Default |
|---|---|---|---|
| guide | Yes | ||
| api_version | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context by disclosing that the result includes the registry row plus artifact and routing-surface status. It does not contradict the annotations.
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?
The description is a single, well-structured sentence. It front-loads the core action and resource, then appends the relevant status detail without any filler or repetition.
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 simple one-parameter read-only tool with a full output schema and clear annotations, the description provides enough context to select and invoke the tool correctly. Nothing essential is missing.
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?
The schema already fully documents the slug parameter with 100% coverage and a concrete example ('start-a-company'). The description confirms the parameter is the lookup key via 'by slug' but adds no additional semantic detail beyond the schema.
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?
The description states a specific verb ('Get'), a specific resource ('one guide's registry row'), and the identifying criterion ('by slug'). It also distinguishes itself from sibling list tools by emphasizing 'one' guide rather than a collection.
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?
The description clearly indicates this is for fetching a single guide when the slug is already known, and the singular framing contrasts with the sibling list tools. However, it does not explicitly name alternatives or state when not to use it, so it stops short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.