Skip to main content
Glama
Sign In

Nifra docs

by io.github.nifrajs
OverviewDiscussionsAdmin

nifra_runtime

Read-onlyIdempotent

Explain a behavior that differs between Bun, Node, Deno and Cloudflare Workers by symptom. These are runtime behaviors, not Nifra's: request-target and Host handling, pipelining, JSON content-type, engine error messages, recursion depth, .env loading, and runtime-specific APIs. Returns what each runtime does, the fix (and the Nifra option that decides it when there is one), how to verify it, and the versions it was measured on. Call with no args for the index; pass symptom (e.g. "path guard skipped", "env var undefined") and/or runtime to filter.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries to return (default 3, max 5).
runtimeNoFilter to one runtime's entries.
symptomNoWhat you observe (omit for the index).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered; the description instead adds substantive context about what comes back — per-runtime behavior, the fix, the deciding Nifra option, verification steps, and measured versions. It doesn't state whether coverage is exhaustive or how results are ranked when symptom is fuzzy.

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?

Front-loads what the tool does, then scopes it, then explains the call patterns — a sensible order with no filler. The mid-sentence topic enumeration is long but functional for discovery, keeping it just short of ideal.

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?

With no output schema, the description carries the return-value burden and does so: it names the fields of a result (per-runtime behavior, fix, Nifra option, verification, versions). Combined with a fully documented 3-param schema, an agent has everything needed to call and interpret it.

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 100% so the baseline is 3, but the description goes beyond it by supplying concrete symptom phrasings ('path guard skipped', 'env var undefined') that teach the expected free-text vocabulary for the fuzzy search parameter. `limit` is left entirely to the schema, which already documents default 3 / max 5.

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?

Names a specific verb (explain) and a clearly bounded resource (behaviors that differ across Bun/Node/Deno/Workers), and enumerates the exact topics covered. The phrase 'These are runtime behaviors, not Nifra's' sharply separates it from the doc/example/learn siblings.

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?

Explicitly says 'Call with no args for the index; pass `symptom` and/or `runtime` to filter,' giving clear invocation modes. The 'not Nifra's' boundary implies when to look elsewhere, but it never names which sibling (e.g. nifra_docs) handles Nifra-level questions.

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

All Nifra docs toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources