Skip to main content
Glama

vspc_get_company

Read-onlyIdempotent

Retrieves a company's status, reseller, subscription plan, and enabled services by UID or name, excluding owner credentials.

Instructions

One company: status, reseller, subscription plan, services enabled for it (owner credentials are never returned).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "vspc_get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany UID or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful content beyond them: the fields exposed and the security-relevant note that owner credentials are never returned. It does not discuss permissions, error behavior for unknown companies, or response shape, keeping it below a 5.

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?

A single compact sentence with no wasted words, and the most important scoping fact ('One company') is front-loaded. Its fragmentary grammar ('One company: ...') and slightly awkward phrasing ('services enabled for it') keep it from being polished.

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 single-parameter read tool with full schema coverage and clear annotations, the description supplies the returned field summary and a credentials note, which is sufficient. It lacks a note on behavior when no company matches, a minor gap for a lookup tool.

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?

There is one parameter with 100% schema description coverage ('Company UID or name'), so the schema already carries the meaning. The description adds no further detail about accepted identifier formats or lookup behavior, making the baseline 3 appropriate.

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 the specific resource ('One company') and enumerates the key fields returned (status, reseller, subscription plan, services enabled), which implicitly contrasts with the sibling listing tool. The retrieval verb is carried only by the tool name rather than the description itself, so it falls just short of a fully self-contained 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?

The phrase 'One company' implies this is the single-record lookup as opposed to a listing, giving implicit usage guidance. However, it never explicitly says when to use this versus vspc_list_companies, nor does it state prerequisites such as needing a known company UID or name.

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