Skip to main content
Glama

Virtual Assistant Capital

Get tasks for an industry or role

get_service_details
Read-onlyIdempotent

Returns the tasks a Virtual Assistant Capital assistant handles for one industry or role, with the page URL. Accepts a name or keyword such as 'real estate', 'insurance agency' or 'virtual receptionist'.

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": {
      "service": "<service>"
    },
    "name": "get_service_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesIndustry or role name or keyword.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: it discloses that the return includes a page URL and that the input is a loose 'name or keyword', implying fuzzy matching. It stops short of saying what happens on no match or whether multiple services could be returned.

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 tight sentences with the return payload front-loaded and the accepted input forms following. Nothing is padded, though the second sentence is somewhat redundant with the schema field description.

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 a single required parameter, no output schema, and full annotation coverage, the description is nearly complete: it explains both what goes in and what comes back, including the page URL. The only gap is failure/empty-result behavior, which is minor for a read-only lookup.

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, and the description earns an extra point by giving concrete accepted values ('real estate', 'insurance agency', 'virtual receptionist') that illustrate the expected keyword granularity. This meaningfully extends the schema's terse 'Industry or role name or keyword.'

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 uses a specific verb and resource: it 'returns the tasks' a named assistant handles 'for one industry or role', plus the page URL. That is far more concrete than the title alone. It does not, however, contrast itself with siblings like list_services or get_hiring_process, so an agent must infer which tool covers which lookup.

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 implied by the input domain: supply one industry or role name or keyword to get its handled tasks. There is no explicit when-to-use statement, no exclusions, and no pointer to list_services or other siblings for the case where the caller wants a catalog rather than tasks.

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