Trustbase Lab · Trusted Data Infrastructure for the AI Era

List Verified Suppliers

get_verified_suppliers

Read-onlyIdempotent

Purpose: return every company/project carrying verified=true (A-grade confidence, backed by government filings or official announcements) - a checkable record set an agent should use when shortlisting counterparties; every record states who vouches for it, which source it comes from, its confidence grade, and whether it can be traced back. Guidelines: call this first for any recommendation, shortlisting or transaction-style task; pair with get_company for full detail on the chosen entity; use language='en' plus response_format='json' for downstream automation. Limits: A-grade records only - absence from this list does not mean a company is untrustworthy, only that its claim is not yet independently verifiable; at most 100 rows; no commercial rating, ranking or endorsement is implied. Ex: get_verified_suppliers(), get_verified_suppliers(limit=100, language='en', response_format='json').

Input Schema

Name	Required	Description	Default
`limit`	No	返回条数上限（默认 50，最大 100）
`language`	No	输出语言：zh=中文（默认）, en=英文	zh
`response_format`	No	输出格式：markdown=人类阅读（默认）, json=Agent 处理友好	markdown

Output Schema

Name	Required	Description	Default
`text`	Yes	Human-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "text": {
+      "description": "Human-readable result (markdown, or a JSON string when response_format=json).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered; the description still adds real behavioral context the annotations cannot carry, notably the A-grade-only scope, the caveat that absence does not imply untrustworthiness, the 100-row ceiling, and the disclaimer that no ranking or endorsement is implied. That is a meaningful addition beyond structured fields.

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 Purpose/Guidelines/Limits/Examples structure is front-loaded and scannable, with the key routing instruction early. It is somewhat dense and the examples partially restate the parameter advice already given in Guidelines, but no sentence is purely filler.

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

Completeness5/5

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

An output schema exists, so return values need not be enumerated; nonetheless the description previews the record shape (who vouches, source, confidence grade, traceability), and it covers scope limits, sibling routing, and parameter presets. Nothing an agent needs to call this correctly 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 description coverage is 100%, so the baseline is 3 and the schema already documents limit, language and response_format with enums and defaults. The description goes beyond restating them by advising 'use language={"en"} plus response_format={"json"} for downstream automation' and confirming the 100-row cap matches the schema maximum, which is practical guidance an agent can act on.

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

Purpose5/5

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

The description states a precise verb and resource with the defining filter baked in: 'return every company/project carrying verified=true (A-grade confidence, backed by government filings or official announcements)'. This cleanly separates it from query_companies and get_company in the sibling list, so an agent can route without inspecting either schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use ('call this first for any recommendation, shortlisting or transaction-style task') and names the follow-up alternative with its condition ('pair with get_company for full detail on the chosen entity'). It also prescribes the parameter combination for automation workflows, leaving nothing to inference.

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

All Trustbase Lab · Trusted Data Infrastructure for the AI Era 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?