Skip to main content
Glama

SOQVER business facts (SO4AG)

List sources

list_sources
Read-only

List published SO4AG sources (organisations) with role, revision and claim count. By default only sources a company published or confirmed itself; include_proposals adds unconfirmed proposals prepared from public websites.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_proposalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint already covering the safety profile, the description adds genuinely useful context: the data scope is restricted to published sources, the default filter excludes unconfirmed proposals, and the record shape (role, revision, claim count) is disclosed. Missing are any notes on pagination, ordering, or volume limits.

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

Conciseness5/5

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

Two sentences, zero filler. The default behavior is front-loaded before the opt-in flag, which matches the order an agent needs to reason about them.

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 read-only, one-parameter listing tool with no output schema, the description covers scope, default filtering, the flag's effect, and the returned fields. Only minor operational details (ordering, pagination) are absent.

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 0%, so the description carries the full burden for the single parameter, and it does explain what include_proposals does and what the default (false) yields. It does not spell out the boolean type or the exact boundary of "prepared from public websites," but the semantics are clear enough to invoke correctly.

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 verb and resource ("List published SO4AG sources (organisations)") and names the fields returned (role, revision, claim count). It does not distinguish itself from siblings like get_source or check_claim, so an agent must infer that this is the collection-level read versus a single-source lookup.

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?

"By default only sources a company published or confirmed itself" establishes the default scope, and "include_proposals adds unconfirmed proposals prepared from public websites" tells the agent when to expand it. There is no explicit exclusion or pointer to alternatives such as get_source for single-record detail.

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