Plumbline: OFAC SDN sanctions screening, SEC financials and company checks from public registries

Read a requirement as it stands

get_requirement

Read-onlyIdempotent

A Plumbline requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it.

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>",
      "id": "<id>",
      "token": "<token>"
    },
    "name": "get_requirement"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The requirement id from an earlier answer
`slug`	Yes	The service, from list_propositions
`token`	Yes	Its private token (also the receipt token of the request it is sent as); keep it private

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already establish that this is a safe, idempotent read. The description adds useful context about returned contents: provenance, replacement history, open questions, unread words, send status, and any offer. It does not describe pagination, formatting, or access constraints beyond what the schema covers.

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 description is a single front-loaded sentence with no filler. It is dense and somewhat cryptic, but every phrase contributes to describing the requirement’s state.

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 burden of explaining returned content and does so by listing provenance, replacements, open questions, unread words, send status, and offers. Combined with fully documented parameters and read-only annotations, it is broadly complete for a simple read tool.

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 the input schema already explains id, slug, and token. The description adds no parameter-level meaning beyond that baseline.

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

Purpose3/5

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

The description identifies the resource (“a Plumbline requirement”) and sketches its contents, implying a read of the current state. However, it never states the retrieval verb explicitly and does not distinguish this tool from siblings such as edit_requirement, interpret_requirement, or send_requirement.

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?

There is no explicit guidance on when to use this tool versus alternatives. “As it stands” hints at reading current state rather than editing or sending, but the agent must infer that contrast.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Plumbline: OFAC SDN sanctions screening, SEC financials and company checks from public registries tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?