Skip to main content
Glama

Managed Nerds

check_fit

Read-onlyIdempotent

Would Managed Nerds take on this business? No contact details, nothing stored, no prices. All fields optional; more give a firmer answer. Returns fit (yes, partial, ask_a_person, no), reasons and the next step.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
seatsNo
stateNo
tenantNo
countryNo
platformsNo
has_own_rmmNo
has_it_staffNo
service_lineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 bar is low. The description adds genuinely useful context beyond them: no contact details are needed, nothing is persisted, and no pricing is returned, which tells an agent this is a safe pre-sales triage call. It also discloses the return shape and the four verdict categories, though it doesn't explain what 'ask_a_person' triggers.

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?

Three short sentences, front-loaded with the framing question, followed by constraints and then the return contract. Every sentence carries information; the only minor weakness is the colloquial phrasing of the opening, which is slightly less precise than a direct verb statement.

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?

There is no output schema, and the description does list the return fields, which covers the biggest gap. But for a nine-parameter scoring tool with zero parameter documentation, the description leaves the agent guessing how to fill the schema meaningfully, and it gives no sense of decision thresholds or what 'partial' versus 'ask_a_person' means in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across nine parameters, so the description carries the full burden and does not meet it. It only states that all fields are optional and that more inputs yield a firmer answer, which the schema's empty required list already implies. None of city, seats, tenant, platforms, has_own_rmm, has_it_staff or service_line is given meaning or examples, and the agent must guess which fields actually move the verdict.

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 opening question plus the enumerated return values ('fit (yes, partial, ask_a_person, no), reasons and the next step') make clear this is a qualification/eligibility check for the business. It is distinguishable from siblings like check_domain or check_ai_readiness, which evaluate specific artifacts rather than overall fit. It is framed as a question rather than a verb+resource, which costs it a point.

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?

The description implies early-stage qualification ('no contact details, nothing stored, no prices') and says more fields produce a firmer answer, which nudges an agent toward using it before request_full_quote or preliminary_estimate. However, it never names an alternative or states when this should be preferred over them, so the routing is left 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