Skip to main content
Glama
nerdit-ai

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capabilities

Query the daemon first to learn its version, caller quotas, URL grammar and supported backends in one read, avoiding endpoint probing. Admin callers also get proxy address and path details.

Instructions

Describe this daemon: version, caller role/quotas, URL grammar, backends.

    Role-aware, pure in-memory read — call it first to learn what the
    daemon can do (buildpacks, model backends, proxy mode and public-URL
    shape, deploy limits, git allowlist, feature flags) instead of probing
    endpoints. Admin callers additionally receive ``proxy.admin_addr`` and
    the ``paths`` block.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it declares 'pure in-memory read' and notes role-aware behavior where admin callers receive additional fields. It does not discuss failure modes, caching, or permission requirements in more detail, but the key safety profile is clear.

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?

The first sentence front-loads the core purpose, and the second paragraph adds useful context. There is mild repetition in 'learn what the daemon can do' following 'Describe this daemon,' and the parenthetical list is long, but overall it is efficient.

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

Completeness5/5

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

There is no output schema, so the description must explain return contents, and it does: version, role/quotas, URL grammar, backends, buildpacks, proxy details, deploy limits, git allowlist, feature flags, plus admin-only fields. That is complete enough for a zero-parameter introspection call.

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, so parameter semantics are not applicable; baseline 4 applies. The description appropriately adds no parameter information because there is none.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Describe this daemon,' then enumerates what is returned (version, caller role/quotas, URL grammar, backends). It also positions the tool as a first-stop discovery call rather than endpoint probing, which distinguishes it from config/diagnostic siblings like get_config or doctor.

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?

'call it first to learn what the daemon can do ... instead of probing endpoints' provides an explicit trigger and an alternative behavior. It does not explicitly state when not to use it or name sibling alternatives, so it stops short of the top score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools