Skip to main content
Glama

Virtual Assistant Capital

Get plans and pricing

get_plans_and_pricing
Read-onlyIdempotent

Returns Virtual Assistant Capital's published virtual assistant plans, monthly prices in US dollars, hours and standard terms.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real information beyond them: it returns only *published* plans (implying custom or negotiated pricing is not included), prices are denominated in US dollars, and terms are the standard ones. That scoping and currency detail is exactly the kind of context annotations cannot convey.

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 sentence that front-loads the verb and resource, then lists contents in a compact parallel series. Every clause (plans, USD prices, hours, terms) earns its place by telling the agent what comes back.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No parameters, no nested objects, and no output schema — so the description carries the burden of describing return contents, and it does so explicitly by naming plans, monthly prices with currency, hours, and terms. For a zero-argument catalog read with safety covered by annotations, nothing an agent needs is missing.

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?

The tool takes zero parameters, so the baseline is 4 per the rubric; however the description adds nothing here because there is nothing to disambiguate. It correctly leaves parameter discussion out rather than padding, but contributes no extra semantic value on this dimension.

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?

Specific verb ('Returns') plus a clearly bounded resource (published virtual assistant plans) with the exact contents enumerated: monthly prices in USD, hours, and standard terms. An agent can tell this is a read of the public price catalog rather than service details or cost comparisons. It stops short of naming the closest sibling (compare_cost_with_local_hire or get_service_details) to sharpen the distinction.

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 by the enumerated contents: an agent can infer 'call this when you need plan hours, prices, or terms.' There is no explicit when-to-use statement and no exclusion such as 'use compare_cost_with_local_hire instead when the user wants a local-hire cost comparison,' which is the most likely confusion given the sibling set.

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