Skip to main content
Glama

vspc_list_companies

Read-onlyIdempotent

Lists companies managed in VSPC, sorted by name with UID and status, so you can select a company UID or name for use in other tools.

Instructions

Companies (clients) managed in VSPC, sorted by name: UID, name, status. Use a UID or name from here as company in the other tools.

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": "vspc_list_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOnly items whose name contains this text (case-insensitive).
limitNoPage size (VSPC maximum 500).
offsetNoItems to skip (for the next page).
statusNoOnly companies with this status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds the default sort order and the projected field set, but says nothing about pagination behaviour or what an empty result means, which is where the remaining ambiguity lies.

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?

Two short sentences, front-loaded with the resource and its returned fields, followed by the actionable chaining hint. No filler; only the missing verb keeps it from being maximally tight.

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 no output schema, the description compensates by enumerating the returned fields and the sort order, which is the key information an agent needs. For a four-parameter, fully documented read-only list tool this is close to complete; only pagination expectations are left to the schema.

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%, with name, limit, offset and status all documented including bounds and enum values. The description adds no filtering semantics or format detail beyond that, so the baseline 3 applies.

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 names the resource (companies/clients in VSPC), the ordering (sorted by name), and the returned fields (UID, name, status). The list verb is implied by the tool name rather than stated, and it does not explicitly contrast with vspc_get_company, but the scope is unmistakable.

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?

It gives a useful downstream-chaining hint: take a UID or name from here and pass it as `company` to the other tools. What it never says is when to prefer this over vspc_get_company for a single known company, so the when-to-use guidance is implied rather than explicit.

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