Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

list_vendors

Read-only

Retrieves active vendors from the system of record to help identify valid vendor records for invoice matching and payment workflows.

Instructions

List active vendors in the system of record.

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_vendors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and openWorldHint=false, so the safety profile is covered. The description adds real context by scoping results to 'active' vendors in the system of record, implying inactive vendors are excluded, but says nothing about pagination, sorting, or result size.

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?

A single front-loaded sentence with no filler. The filter ('active') and source ('system of record') are stated before any would-be elaboration, so nothing needs trimming.

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 zero parameters, a full output schema, and annotations covering read-only behavior, the definition is nearly complete. The remaining ambiguity is what counts as 'active' and whether the result set is bounded, which is minor for a simple list tool.

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?

There are no input parameters, so there is no parameter semantics to document; the baseline of 4 applies. The only semantic constraint, 'active', is carried by the description rather than the empty schema.

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?

The description gives a specific verb and resource ('List active vendors') plus scope ('active', 'in the system of record'). It is immediately distinguishable from siblings like list_inbox or list_purchase_orders because the resource is named, though it does not explicitly call out that it differs from them.

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?

Usage is only implied: the agent can infer this is the roster lookup for vendor data, but there is no statement of when to prefer it over other lookups (e.g., get_proposal or check_invoice) or any prerequisite. For a zero-parameter read tool this is adequate but thin.

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