Skip to main content
Glama

Attify

Define a term

define_term
Read-onlyIdempotent

What a term of AI agent verification means (resolution rate, handoff, containment, meetings booked, show rate, evidence tier, provenance...): Attify's glossary definition, with how vendors' own definitions differ where they do, and each standard's own definition in its own words, with the anchor to cite. Nothing else is guessed: an unknown term says so.

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": {
      "term": "<term>"
    },
    "name": "define_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe term, e.g. "audited resolution" or "no-show rate".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint, idempotent, non-destructive, closed-world), so the description does not need to restate safety. It earns credit by disclosing what the response contains: vendor definition differences, a standard's own verbatim definition, and the anchor needed for citation. It also states explicitly that unknown terms return a specific 'not found' signal rather than a fabricated answer, which is genuinely useful behavior 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?

The useful content comes first: the definition, then the structure of the answer, then the no-guessing guarantee. It is dense but every clause (vendor divergence, verbatim standard text, citable anchor, unknown-term handling) carries distinct information. The parenthetical word list and the trailing ellipsis make it slightly heavier and less scannable than it could be.

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

Completeness4/5

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

There is no output schema, so the description must explain the return payload, and it does so in enough detail to set expectations: the layered answer with anchors, plus the unknown-term case. For a one-parameter lookup tool this is nearly complete. The only shortfall is that it does not say how the response is presented (for example, whether the sections are combined or separate), which keeps it at a 4.

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?

With a single required parameter at 100% schema coverage and a string description already supplying examples, the schema carries the load. The description adds only indirect guidance on the parameter via its own example list of terms. That matches the baseline-3 expectation when the schema already documents the inputs.

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

Purpose4/5

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

The description uses a clear define/term pairing and lists exactly what the term covers (resolution rate, handoff, containment, show rate, evidence tier, provenance), so an agent knows the domain precisely. It also outlines the shape of the answer: Attify's glossary definition, vendor differences, and each standard's own wording with a citable anchor. It does not differentiate itself from adjacent siblings such as explain_check or get_standard, which keeps it below a 5.

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 intended use, looking up the meaning of an AI-agent-verification term, is strongly implied by the parenthetical examples and by the note that the tool will not guess outside that scope. However, the description never says when to choose this over explain_check or get_standard, and gives no explicit exclusion or prerequisite. That is adequate but clearly one-sided guidance.

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