Skip to main content
Glama

disclosedby, the subprocessor record

Walk your vendors to a company or a country

in_chain

Given the companies a reader buys from, every path from that list to one company, or to a country: named directly, or named on the own list of a company they name (a fourth party, or sub-subprocessor). Each step is a list's own row, with its purpose and location as written, and the versions each run of it started and ended between; on a date, the versions held on or before it. A country is reached through hand-checked headquarters, of the company or of its group. A second step is a different relationship, quoted from a different page. Names that matched nothing, companies with no list read and rows that did not resolve come back beside the paths. It says who to ask, never who is harmed. Needs a key on an account with Follow your vendors running: this is part of the subscription on disclosedby.com. 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": {
      "companies": "<companies>",
      "target": "<target>"
    },
    "name": "in_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoOptional ISO date: the walk as the lists held it then.
targetYesThe company to look for, or a country by name or code.
companiesYesThe companies the reader buys from, by domain or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / on
      Added value: +{
      +  "description": "Optional ISO date: the walk as the lists held it then.",
      +  "type": "string"
      +}
    • changedInput schema / properties / target / description
      Previous value: -"The subprocessor to look for."New value: +"The company to look for, or a country by name or code."
  2. First observed

TDQS

A3.5/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 substantial work: it discloses the subscription/auth requirement, the date semantics (versions held on or before the given date, otherwise the versions each run started and ended between), and the returned anomalies (names that matched nothing, companies with no list read, unresolved rows). It also states a scope limitation ('says who to ask, never who is harmed') and legal-use restrictions (no lead lists, no prospecting feeds, citation and read-date obligations). It stops short of cost, rate limits, pagination, or response size for a 200-company input.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Core behavior is front-loaded in the first sentence, but the prose is long, clause-heavy and fragmentary ('A second step is a different relationship, quoted from a different page'), which slows parsing. A sizeable share of the text is licensing boilerplate about citation, extraction and prohibited reuse; it is relevant but could be compressed to one sentence. No pure padding, but structure could be much tighter.

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 3-parameter, no-annotation, no-output-schema traversal tool, the description covers purpose, input meaning, date-versioning semantics, the shape of a step (a list's own row with purpose, location, version range), and the accompanying non-resolved results. Gaps remain around response shape specifics and operational limits, but nothing essential for calling it correctly with a target and a company list is missing.

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%, so the baseline is 3, and the description adds real meaning on top: 'on' is not just a date filter but resolves each step to the versions of the list held at that date; 'target' accepts either a company or a country, with countries reached via hand-checked headquarters of the company or its group; 'companies' is defined as what the reader buys from, by domain or name. It does not clarify how ambiguity between company name and country name is resolved when target could match both.

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 concretely states the operation: enumerate every path from a supplied list of purchased-from companies to a target company or country, including indirect naming via a vendor's own list (fourth party / sub-subprocessor). The resource and scope are specific, but there is no explicit verb ('returns', 'finds') and the opening clause is a sentence fragment, so the agent must reconstruct the operation. The title carries the verb ('Walk your vendors'), and the sibling tools (resolve, named_by, as_of) are never mentioned to sharpen the distinction.

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?

The description implies the use case (walk a reader's vendor base toward a target), but never states when to choose this over as_of, named_by, resolve, or changes, nor any exclusions. It does state a hard precondition — an account key with 'Follow your vendors' running — which is useful, but that is an eligibility gate rather than when-to-use guidance. An agent has to infer the boundary with as_of from the one clause about dates.

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