Synthex Forge — x402 Paid Agent Services

Get Bureau Reputation Corpus

get_bureau_reputation_corpus

Read-onlyIdempotent

a reputation report derived ONLY from the Bureau's own real corpus of. use it rather than get_bureau_reputation for bureau reputation corpus, not bureau reputation; an object with 16 fields including as_of, basis.

Input Schema

Name	Required	Description	Default
`as_of`	No	The date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
`target`	Yes	Must not be empty. The handler rejects an empty value with 400 `bad_request`.

Output Schema

Name	Required	Description
`as_of`	No	The date the answer is computed as of.
`basis`	No	The `basis` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`reason`	No	Why the verdict was reached.
`target`	No	The `target` field of the response.
`verdict`	Yes	The decision this tool returned.
`clean_ratio`	No	The `clean_ratio` field of the response.
`consistency`	No	The `consistency` field of the response.
`min_required`	No	The `min_required` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`last_observed`	No	The `last_observed` field of the response.
`first_observed`	No	The `first_observed` field of the response.
`observation_count`	No	The `observation_count` field of the response.
`clean_observations`	No	The `clean_observations` field of the response.
`defect_observations`	No	The `defect_observations` field of the response.
`seconds_since_last_defect`	No	The `seconds_since_last_defect` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 31, 2026

addedOutput schema / properties / as_of

Added value: +{
+  "description": "The date the answer is computed as of.",
+  "type": "string"
+}

addedOutput schema / properties / basis

Added value: +{
+  "description": "The `basis` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / clean_observations

Added value: +{
+  "description": "The `clean_observations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / clean_ratio

Added value: +{
+  "description": "The `clean_ratio` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / consistency

Added value: +{
+  "description": "The `consistency` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / coverage_gaps

Added value: +{
+  "description": "The `coverage_gaps` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / defect_observations

Added value: +{
+  "description": "The `defect_observations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / first_observed

Added value: +{
+  "description": "The `first_observed` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / last_observed

Added value: +{
+  "description": "The `last_observed` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / min_required

Added value: +{
+  "description": "The `min_required` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / observation_count

Added value: +{
+  "description": "The `observation_count` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / seconds_since_last_defect

Added value: +{
+  "description": "The `seconds_since_last_defect` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / target

Added value: +{
+  "description": "The `target` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds one genuinely useful constraint—results are derived only from the Bureau's own corpus—but undercuts it by also restating return structure ('an object with 16 fields') that the output schema already provides.

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

Conciseness2/5

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

The text is short but structurally broken: an incomplete first sentence ('...corpus of.') followed by a semicolon-joined run-on mixing usage guidance and return shape. The lack of a complete leading sentence undermines front-loading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, full schema coverage, and an output schema, the remaining burden is sibling differentiation and scope. The alternative is named, but the truncated sentence leaves 'what corpus' and 'what the report measures' undefined, which is a meaningful gap for a domain-specific reputation 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% and both parameters are well documented in the schema (as_of format/reproducibility, target non-empty constraint). The description adds no parameter meaning beyond mentioning 'as_of' incidentally in the output field list, so baseline 3 applies.

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 names the resource ('reputation report derived ONLY from the Bureau's own real corpus') and distinguishes it from get_bureau_reputation, but the opening sentence is truncated ('corpus of.') so the scope is never fully stated. An agent gets the gist but not a clean, specific definition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative ('use it rather than `get_bureau_reputation`') and gives the selecting condition ('for bureau reputation corpus, not bureau reputation'). The phrasing is awkward and run-on, but the routing instruction is unambiguous.

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

All Synthex Forge — x402 Paid Agent Services 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.