Skip to main content
Glama

Managed Nerds

ask

Read-onlyIdempotent

A question about Managed Nerds (services, who we work with, how things work, our how-to posts), answered only from our own pages, with the pages it used. Also "my X isn't working" questions (printer offline, Outlook rules, slow PC, locked out, fake virus pop-up, hacked WordPress, Microsoft 365 sign-in from another country...): when a step-by-step fix post matches, each source carries applies_to and last_checked, and still_stuck says how a person can help. Never a price (those are in our free guides). 100 answers a day across all agents.

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": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

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?

Beyond the annotations (readOnly, closed-world, idempotent), the description discloses grounding ('answered only from our own pages'), citation behavior ('with the pages it used'), response fields (applies_to, last_checked, still_stuck), and a real operational limit ('100 answers a day across all agents'). That is meaningful behavioral context an agent cannot get from structured fields. It does not say what the response looks like when no source matches, which leaves one gap.

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?

The purpose is front-loaded in the first clause, which is good, but the body is a long string of parentheticals and marketing-flavored framing that a reader must sift. The rate-limit sentence is tacked on at the end rather than grouped with other behavioral facts. Trimming the example lists and the 'never a price' aside into one clause would lose nothing.

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 grounded Q&A tool with no output schema, the description covers what the agent most needs: what it answers from, what comes back (citations plus troubleshooting metadata), what it will refuse (pricing), and throughput limits. The only real omission is the fallback behavior when nothing relevant is found, partially addressed by the 'still_stuck' mention.

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 0% for the single 'question' parameter, so the description carries the burden — and it does, enumerating the categories and even the phrasing style of valid questions ('my X isn't working', symptom lists) and the exclusion (no pricing questions). It does not mention the 300-character cap, but that is available in the schema itself.

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 specific verb (answer) and resource (a question about Managed Nerds), and scopes it to 'answered only from our own pages, with the pages it used,' which distinguishes it from a raw site search or a listing tool. It also carves out a second mode (troubleshooting 'my X isn't working' questions). The branding-heavy phrasing ('Managed Nerds') and long parenthetical lists make the core purpose slightly harder to extract than it needs to be.

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?

It gives clear when-to-use triggers: service/practices/how-things-work questions and step-by-step fix questions with concrete symptoms (printer offline, Outlook rules, locked out, hacked WordPress). It also gives a when-not: 'Never a price (those are in our free guides),' routing pricing to the guides. It stops short of naming a sibling tool explicitly, so the agent must infer which sibling handles non-answer lookups.

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