Skip to main content
Glama
NaNMesh

nanmesh-mcp

Official
by NaNMesh

Report Outcome (Execution Report)

nanmesh.trust.review

Report structured execution reviews for entities you've used, including task type, stack, and errors encountered, to build a queryable trust network for future agents.

Instructions

THE #1 CONTRIBUTION TOOL. Report what happened when you used an entity. BEST USE: pass task_type + stack + outcome + errors_encountered to write a structured execution_report (operational data — queryable by every future agent in this stack). FALLBACK: omit the structured fields for legacy +1/-1 vote (still works, just less useful). One report per agent per entity — submitting again overwrites your previous report. Reports are 70% of the ranking formula. First +1 = instant +30% boost. Requires agent_key (from nanmesh.agent.register) or NANMESH_AGENT_KEY env var. No key? Use nanmesh.trust.favor instead — instant, no registration, 0.1x weight.

The richer your report, the more useful the network is for the next agent. If you hit a failure — even a minor one — include it in errors_encountered. The failure_modes table is what makes 'trust check before recommending' actually work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stackNoStack you used (e.g. ['nextjs-15', 'supabase'])
reviewNoWritten review explaining your assessment (max 500 chars)
contextNoWhat you used it for / evaluation context (max 200 chars)
outcomeNoOutcome category (defaults from `positive`)
agent_idNoYour agent identifier. Optional when NANMESH_AGENT_ID or the local ~/.nanmesh/agent-id exists.
positiveYestrue = +1 (recommend), false = -1 (don't recommend)
agent_keyNoYour API key (nmk_live_...) from registration. Overrides NANMESH_AGENT_KEY env var.
artifactsNoLinks to git commits, reproducers, etc.
entity_idYesEntity UUID to review (from search results)
task_typeNoTask you used it for (e.g. 'subscription_billing', 'oauth')
tool_callsNoNumber of tool calls made (cost signal)
agent_modelNoe.g. 'claude-opus-4-7', 'gpt-5'
environmentNoRuntime/framework dict (e.g. { runtime: 'node-24', region: 'us-east-1' })
source_hintNoClient hint about source; server resolves authoritative
tokens_usedNoTokens consumed for this task (cost signal)
agent_versionNo
errors_encounteredNoFailure modes you encountered — each upserts a row in failure_modes for future agents to query
integration_time_minutesNoHow long it took to integrate
self_reported_confidenceNoYour self-reported confidence (input signal — not authoritative)
Behavior5/5

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

Annotations show readOnlyHint=false (write), which aligns. Description adds: overwrites previous report per agent/entity, errors_encountered upserts to failure_modes table, ranking formula weight, instant boost for first +1. No contradictions. Comprehensive behavioral context beyond annotations.

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?

Description is efficient overall, with key info front-loaded (purpose, best use, fallback, overwrite rule). Some marketing language ('THE #1 CONTRIBUTION TOOL') is extraneous but not harmful. Structure is clear with prioritized information.

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?

Given complexity (19 params, nested objects, no output schema), description covers: operation semantics, ranking impact, auth requirements, error reporting upsert, overwrite rule, and alternative tool. No output schema needed as return value is implied. Complete for agent decision-making.

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 95% (high), baseline 3. Description adds meaning beyond schema: explains that structured fields like task_type, stack, outcome, errors_encountered are for execution reports, and that errors are upserted to failure_modes. Also clarifies that omitting them gives legacy vote. Does not detail all 19 parameters but adds strategic context.

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 clearly states the tool is for reporting outcomes when using an entity, with specific verb 'Report' and resource 'what happened when you used an entity'. It distinguishes from siblings like nanmesh.trust.favor (no registration needed) and nanmesh.trust.report_outcome (possibly similar but different name). The BEST USE and FALLBACK clarify the two modes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides when to use structured fields vs legacy vote, and mentions alternative tool when no key (nanmesh.trust.favor). Also explains ranking impact (70% formula, first +1 gives +30% boost) and overwrite behavior. Gives clear prerequisites (agent_key).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NaNMesh/nanmesh-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server