Skip to main content
Glama

disclosedby, the subprocessor record

What a list said on a date

as_of

What one company's list said on a given date, from the reading this record holds nearest before it, with that reading's own date, its web-archive capture where there is one, its source and its digest. Says so when the date is earlier than the first reading held. 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": {
      "company": "<company>",
      "date": "<date>"
    },
    "name": "as_of"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesISO date, e.g. 2024-01-01.
companyYesA company with a list on this record: its domain (notion.so) or its name (Notion). One company per call.

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?

With no annotations supplied, the description carries the full burden and does substantial work: it defines the nearest-before fallback, discloses the returned components (reading date, web-archive capture, source, digest), specifies out-of-range behavior, states the auth/subscription requirement, and signals read-only use ('Free to read, cite and link'). It stops short of describing the response shape or ordering when multiple readings tie, but the behavioral profile is 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.

Conciseness3/5

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

The purpose and fallback semantics are front-loaded and efficient, but roughly half the text is licensing and anti-scraping boilerplate that, while legally relevant, crowds out tool mechanics. Several sentences ('Every row is a dated quote...', 'The compilation is protected...') do not help an agent decide or invoke.

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 rightly enumerates what comes back — the reading, its date, the archive capture, source and digest — and covers auth, the out-of-range case, and the single-company constraint. Enough to call it correctly, though the returned structure is described only in prose, leaving field shapes to be discovered at runtime.

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 a 3 baseline applies, but the description adds real meaning: `date` is not just an ISO date but the anchor for a nearest-before lookup, and `company` is constrained to one company per call with a domain-or-name form. These clarify behavior the schema's per-field text does not.

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 states a specific operation: return what one company's list said on a given date, using the nearest reading held before that date. That is a distinct, verb-like retrieval with clear temporal semantics. It does not explicitly contrast itself with siblings such as `changes` or `list`, which is the only thing separating it from 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?

Prerequisites are stated ('Needs a key on an account with Follow your vendors running') and one edge case is handled ('Says so when the date is earlier than the first reading held'). However, there is no explicit statement of when to use this instead of `list` (current state) or `changes` (what moved), so the choice between siblings is only implied by the word 'date'.

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