Skip to main content
Glama

Managed Nerds

request_service

Only when your user asked: a quote from a person for SEO, secure WordPress or a project (no prices here; a reply by email within one business day). service_line seo needs website, service area, main services and whether Google Analytics and Search Console are set up; ad management comes only with SEO (seo.wants_ads, ad_platforms, ad_budget 500-1500, 1500-5000 or 5000+). secure_wp needs site URL, hosting provider, DNS provider, e-commerce and hacked-before. project needs project.slug and project.details (answer the project's quote_questions from list_projects).

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_line": "<service_line>",
      "contact": "<contact>",
      "business": "<business>",
      "user_request": "<user_request>",
      "user_approved": "<user_approved>"
    },
    "name": "request_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
seoNo
notesNo
contactYes
projectNo
businessYes
secure_wpNo
service_lineYes
user_requestYes
user_approvedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive write into a closed system. The description adds real context beyond them: no pricing output, an email reply within one business day, and the constraint that ad management is only available alongside SEO. It does not state what happens on success (ticket ID, delivery details) or whether repeat submissions duplicate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is dense but packed into one long run-on sentence with semicolons, making per-branch requirements hard to scan. The user-approval gate is correctly front-loaded, yet the whole block would parse far better as separate per-service lines.

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

Completeness3/5

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

For a mutation tool with nine parameters, nested objects and no output schema, the description covers most service-specific payloads but omits the shared required fields that determine whether the call succeeds or is rejected. An agent cannot tell from this text what user_request must contain or what user_approved=true signifies.

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?

With 0% schema coverage and only type:object stubs, the description carries nearly all the load and does so for seo, secure_wp and project — naming fields such as service area, DNS provider, hacked-before, project.slug and project.details, plus ad_budget enum values. It leaves the equally required contact, business, user_request and user_approved undescribed, which is the main gap for a 9-parameter nested tool.

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 states a routed quoting resource: "a quote from a person for SEO, secure WordPress or a project," and enumerates the three service_line branches. It stops short of naming how it differs from near-siblings like request_full_quote or request_seo_check, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

A strong gate is front-loaded: "Only when your user asked" tells the agent not to call unprompted, and "no prices here" directs pricing intent elsewhere. It also ties the project branch to list_projects for quote_questions, but never names the alternative request tools by name, leaving some routing to inference.

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