Skip to main content
Glama

disclosedby, the subprocessor record

Changes across a reader's own list

changes_across

The dated changes to the lists of several companies at once, each carrying the two readings it came from. The same facts as changes, gathered for one reader's own list of companies. 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>"
    },
    "name": "changes_across"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOptional ISO date; only changes on or after it.
companiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 auth/subscription requirement, the row semantics ('each carrying the two readings it came from', 'a dated quote of a company's own published page'), the citation obligation, and explicit re-use prohibitions. It omits operational behavior such as pagination, per-call limits, or error conditions.

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?

The purpose is front-loaded in the first two sentences, which is good. Roughly half the text is licensing/citation boilerplate that repeats the same idea ('cite the page and the read date', 'the compilation is protected', 'may never be compiled into a lead list') and dilutes the selection-relevant signal.

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 two-parameter read tool with no output schema and no annotations, the description covers access requirements, what each row contains, and legal constraints on use. The main gap is the format of `companies` entries and any paging behavior for up to 200 companies.

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 50%: `since` is documented in the schema while `companies` is only typed as an array of strings with maxItems 200. The description hints that the list is the reader's own followed vendors ('gathered for one reader's own list', 'A key is one reader's own use'), which adds some constraint meaning, but it never states the accepted identifier format for each company.

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 resource ('the dated changes to the lists of several companies at once') and explicitly positions itself as 'the same facts as `changes`, gathered for one reader's own list of companies', which distinguishes it from the singular sibling. The verb is implicit ('gathered') rather than stated as a clear action, but an agent can tell what it returns.

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 prerequisite is spelled out ('Needs a key on an account with Follow your vendors running'), which tells the agent when this will work. However, it never says explicitly when to prefer this over `changes` or the other siblings — the multi-company scope is only implied by contrast, and no when-not guidance is given.

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