Skip to main content
Glama

get_guidelines

Read-only

Return writing rules. posting is for reading a job posting. resume is for writing or reviewing a resume. cover_letter is for writing or reviewing a letter.

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": {
      "topic": "<topic>"
    },
    "name": "get_guidelines"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that the returned content is writing rules scoped by topic, with no indication of return size, format, or whether guidelines vary in length by topic – modest added value beyond 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.

Conciseness4/5

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

Front-loaded with the core action, then the topic breakdown, with no filler. The fragmented, verbless clauses are terse to the point of ambiguity, but nothing is bloated.

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

Completeness3/5

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

For a single-parameter read tool with annotations and no output schema, the description is minimally sufficient but omits what the rules look like, whether output differs per topic, and how to choose a topic when unsure. The absence of an output schema means some sense of the return payload would have helped.

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

Parameters4/5

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

With 0% schema description coverage, the description must carry the single enum parameter, and it does explain all three values with intended usage contexts. The explanation is somewhat telegraphic and the "posting" clause is the weakest, but each enum member is disambiguated in a way the bare enum names are not.

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?

"Return writing rules" gives a verb and a resource, but "rules" vs. the tool name "guidelines" and the enum topics introduces slight drift. The per-topic clauses do distinguish what each topic covers, yet the phrasing "posting is for reading a job posting" reads ambiguously, and nothing distinguishes this from get_resume or get_cover_letter, which an agent could easily mistake for guideline sources.

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

Usage Guidelines3/5

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

The mapping sentences imply when each topic value applies (posting for reading a posting; resume/cover_letter for writing or reviewing), which is real guidance for choosing a topic. However, there is no explicit when-to-use statement relative to siblings like get_resume or get_schema, and no when-not guidance, so the agent must infer the broader routing.

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