Skip to main content
Glama

Virtual Assistant Capital

List industries and roles

list_services
Read-onlyIdempotent

Lists the industries and roles Virtual Assistant Capital places virtual assistants for, each with a page URL. An optional query filters by keyword, for example 'dental' or 'bookkeeping'.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keyword to filter by.

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered elsewhere. The description adds that the response carries page URLs and that filtering is driven by a free keyword, but says nothing about result counts, ordering, or what happens when the query matches nothing.

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?

Two sentences, zero filler, with what the tool returns front-loaded before the optional filter detail. Nothing could be removed without losing information.

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 single-optional-parameter read tool with rich annotations and no output schema, this covers purpose, return shape, and filter behavior adequately. Only the relationship to the sibling search tool is left unaddressed.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by giving concrete keyword examples ('dental', 'bookkeeping'), which communicate the expected granularity of the filter (a niche term, not an exact industry name).

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 and resource ('Lists the industries and roles Virtual Assistant Capital places virtual assistants for') and adds the return element (each with a page URL). It is clear on its own, but it doesn't distinguish itself from the similar search/list sibling search_guides, so an agent must infer the difference.

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 reader can tell this is a catalog lookup and the 'dental'/'bookkeeping' examples hint at keyword use, but there is no explicit statement of when to call it instead of search_guides or get_service_details, and no note about what an unfiltered call returns.

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