Skip to main content
Glama

List Sources

list_sources
Read-onlyIdempotent

List where the pest treatment provider data comes from, with the license and refresh of each source.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully structured. The description's only added behavioral value is that each source entry carries license and refresh metadata, which is useful but thin. It says nothing about ordering, count, or whether the source list is static.

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?

One sentence, front-loaded with the verb and resource, with the returned attributes appended rather than buried. Nothing is repeated from the name or title and no words are wasted.

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 simple, non-destructive, zero-parameter list tool this covers what an agent needs: what it enumerates and which fields come back. Since no output schema exists, the mention of license and refresh is doing real work in describing the return shape. A brief note on ordering or typical source count would make it fully complete.

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?

The tool takes no parameters, so there is no parameter meaning to convey and the schema cannot be improved upon by prose. Baseline 4 applies. The description correctly avoids inventing filtering options that the empty schema would reject.

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 ('List') and resource ('where the pest treatment provider data comes from'), plus the attributes returned per item (license and refresh). An agent can immediately tell this is a provenance/metadata enumerator rather than a data-record lister, which separates it from siblings like list_products or search_listings. It stops short of naming a sibling it contrasts with, so a 4 rather than 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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. Usage is only implied: an agent would infer this is the call to make when it needs provenance, licensing, or freshness information before trusting the provider data. Adequate for a zero-parameter enumeration tool, but the routing logic is left to inference.

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