Skip to main content
Glama

Managed Nerds

get_profile

Read-onlyIdempotent

Managed Nerds' vendor profile for comparing providers: who they serve (US only; on-site around Augusta, Georgia), services, support hours, products supported and how to buy. No prices.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and idempotency need no restatement. The description adds genuine beyond-schema context: the profile is scoped to a single vendor, covers US-only service with on-site coverage around Augusta, Georgia, and explicitly excludes pricing, which prevents an agent from calling it to answer cost questions.

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?

A single sentence front-loads the resource identity, then enumerates returned fields, and closes with the negative constraint "No prices." Every clause carries information; nothing is repeated from the schema or annotations.

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 zero-argument read tool with no output schema, the description does the work the missing output schema would otherwise do by listing the categories of information returned. Combined with the closed-world annotation and the explicit no-pricing boundary, an agent has enough to call it correctly; only the concrete return shape and formatting remain unspecified.

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?

The tool takes zero parameters and the input schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. Per the zero-parameter baseline this lands at 4; the description correctly avoids inventing parameter language that does not exist.

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 names a specific resource (Managed Nerds' vendor profile) and enumerates its contents: service area, services, support hours, products supported, and how to buy. That is well beyond a tautology and lets an agent tell it apart from sibling tools like list_services or check_fit, which are narrower or diagnostic. It stops short of a crisp verb-first statement, but for a single-resource read tool the scope is unambiguous.

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 phrase "for comparing providers" implies a use case, and "No prices" is a useful exclusion that steers the agent away from expecting pricing data. However, there is no explicit guidance on when to prefer this over check_fit, list_services, or preliminary_estimate, so the routing decision 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