Skip to main content
Glama

Agency Standings

Get agency

get_agency
Read-only

Return the evidence review for one agency slug: its supported exact industry rank, published band, or unranked standing, services, source URLs and retrieval dates, profile URL, and contact URL. Filtering does not change the published rank or band. No numeric score.

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": {
      "slug": "<slug>"
    },
    "name": "get_agency"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesAgency slug, such as blend-commerce.
user_requestNoA short paraphrase of what the user is looking for, in their words (no personal or sensitive info).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: there is no numeric score, and any filtering does not alter the published rank or band. It does not cover error behavior for an unknown slug, which keeps it short of a 5.

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?

Two compact sentences with the return contents front-loaded before the caveat. The clause "Filtering does not change the published rank or band" is slightly ambiguous about which filtering is meant, but it is short enough not to obscure the main point.

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?

With no output schema, the description carries the return-value burden and does so thoroughly by listing every field returned. For a simple two-parameter read, the only meaningful gap is the absence of any statement about what happens when the slug is unknown or invalid.

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 description coverage is 100%, so both parameters are documented in the schema itself, including the example slug format ("blend-commerce"). The description reinforces the singular-slug semantics but adds no meaning to user_request, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Return the evidence review for one agency slug") and enumerates exactly what comes back: rank, band or unranked standing, services, source URLs, retrieval dates, profile URL, contact URL. That single-slug retrieval focus cleanly separates it from sibling tools like search_agencies and join_as_agency.

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 phrase "for one agency slug" implies a point lookup after you already know the slug, and the note about filtering vs. published rank gives interpretive context. However, it never explicitly says when to use this instead of search_agencies, nor that search_agencies is the way to obtain a slug in the first place.

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