Skip to main content
Glama

Attify

Get a published standard

get_standard
Read-onlyIdempotent

A job type's published standard: number, title, version, status, how the claim is reconstructed, the checks, the evidence tiers, the changelog and the full text's address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_standard"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_typeNoOne of "support-resolution" (the default), "sales-meetings", "bookings".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's contribution is enumerating what the response contains, which is genuinely useful since no output schema exists, but it says nothing about size, versioning behavior, or what happens for an unpublished/unknown job type.

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?

One compact sentence with no filler, and the field enumeration is front-loaded with the most identifying items (number, title, version, status). It reads as a fragment rather than a complete sentence, which slightly undercuts clarity, but nothing is wasted.

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 zero-required-parameter read tool this is close to adequate, and the field list usefully substitutes for the missing output schema. However, it leaves out the action framing and any guidance on choosing this tool over its many get_* and explain_* siblings, which is the main risk in this catalog.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter's enum values and default are documented in the schema itself. The description only echoes the concept with the possessive 'a job type's published standard', adding no format or selection guidance beyond the schema. Baseline 3 applies.

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?

The description is a noun phrase enumerating the payload (number, title, version, status, checks, evidence tiers, changelog, full-text address) rather than a verb+resource statement of what the tool does. Combined with the title 'Get a published standard' an agent can infer it fetches a standard for a job type, but the description alone never says 'retrieves' or 'returns', and it offers no differentiation from siblings like get_verdict, get_index, or get_evidence.

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 at all — no condition selecting this tool over get_verdict, get_evidence, or explain_check, and no statement of when a standard is the right artifact to fetch. The only hint is the implicit scoping to a job type.

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