Skip to main content
Glama

styleguide_get

One style guide incl. the active version content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "styleguide_id": "<styleguide_id>"
    },
    "name": "styleguide_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleguide_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full disclosure burden, and it only adds that the active version content is included. It says nothing about whether the call is read-only, what happens if the style guide does not exist, whether authentication or project scoping is required, or what fields come back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is extremely short with no filler, which is good, but it is a sentence fragment that omits rather than compresses information. Brevity here reads as under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter getter this could be adequate, but with no output schema and no annotations, the description must convey both the identifier source and the shape of the returned style guide. It only hints that version content is included, leaving the agent guessing at the rest.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter styleguide_id, and the description provides no compensating meaning — it never names the parameter, its format, or where an agent would obtain a valid ID. A one-param getter would otherwise sit near the baseline, but the undocumented identifier is the sole key to a successful call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"One style guide incl. the active version content" conveys that this fetches a single style guide rather than a list, which loosely distinguishes it from styleguide_list. However, it is a noun fragment with no verb (get/retrieve/read), and it never states the identifier basis for locating the guide, so the purpose is only implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no condition under which to pick this over styleguide_list or glossary_get, and no prerequisites. The singular "one" is the only hint that this is the single-record counterpart to a listing call, and the agent must infer that entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources