Skip to main content
Glama

disclosedby, the subprocessor record

Which company a name refers to

resolve

What company a name on a list refers to, through this record's hand-checked identity table. Exact match only, never a guess: an unknown name comes back unresolved, which is an answer. Free to read, cite and link. Every row is a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

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

Input Schema

NameRequiredDescriptionDefault
nameYesA name as printed on a list, or an alias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: unknown names return unresolved rather than guessing, rows are dated quotes that must be cited with the read date, and extraction/re-use into lead lists or sales tools is prohibited. It omits return shape, rate limits, and what a 'key' actually controls, but the behavioral and legal constraints disclosed go well beyond the schema.

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 behavioral core is front-loaded: what it resolves, then the exact-match rule and unresolved outcome. The licensing block is long and slightly redundant ('Free to read, cite and link' versus 'cite the page and the read date'), and the closing 'A key is one reader's own use' is cryptic, but nothing is padding.

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?

For a one-parameter read tool with no output schema and no annotations, the description covers resolution semantics, the negative-result case, and reuse restrictions. What a successful result contains (fields of the matched company record) is never described, which is the main remaining gap.

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?

Schema coverage is 100% with a single required 'name', so the baseline is 3-4 and the schema already explains the input. The description adds genuine semantics by stating the match is exact and that a miss is a legitimate result, which the schema does not say.

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?

States a specific outcome: which company a name on a list refers to, via a hand-checked identity table, with exact-match-only semantics. An agent knows what it returns (a resolved company or an unresolved answer) but is never told how this differs from siblings like named_by or in_chain.

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?

Usage is implied through 'a name on a list' and the exact-match rule, which tells the agent not to use it for fuzzy lookup. However, none of the six sibling tools are named and no condition selecting resolve over named_by or in_chain is given, so routing is left to inference.

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