Skip to main content
Glama
NaNMesh

nanmesh-mcp

Official
by NaNMesh

List Entities

nanmesh.entity.list
Read-only

List entities in the NaN Mesh trust network with filters for task type, stack, confidence thresholds, and failure severity. Constraint-solver mode provides AI-native entity browsing.

Instructions

List entities in the NaN Mesh trust network. Default: trust_score / evaluation_count / metadata (4.1.1 byte-identical). Constraint-solver mode (any of task_type/stack/min_confidence_*/max_failure_severity/exclude_unresolved_critical, or format='agent'): filters by per-axis confidence thresholds, failure-mode severity, and stack/task match. After browsing, use nanmesh.trust.review (expert) or nanmesh.trust.favor (instant) on entities you've evaluated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort fieldtrust_score
limitNoMax results
stackNoStack overlap filter (e.g. ['nextjs', 'supabase'])
formatNoPass 'agent' for the AI-native list (each entity includes confidence_decomposition + failure counts)
offsetNoPagination offset
categoryNoFilter by category slug
task_typeNoNarrow to a task (e.g. 'subscription_billing', 'oauth')
max_failure_severityNoExclude entities with worse-than-this unresolved failures
exclude_unresolved_criticalNoIf true, drop entities with any unresolved critical failure
min_confidence_api_stabilityNoMinimum api_stability (0..1)
min_confidence_cost_efficiencyNoMinimum cost_efficiency (0..1)
min_confidence_security_postureNoMinimum security_posture (0..1)
min_confidence_documentation_qualityNoMinimum documentation_quality (0..1)
min_confidence_integration_success_rateNoMinimum integration_success_rate (0..1)
Behavior4/5

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

Beyond readOnlyHint annotation, describes default behavior (trust_score/evaluation_count/metadata byte-identical) and constraint-solver mode details (per-axis confidence thresholds, failure severity, stack/task match). No contradiction with 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?

Two sentences with front-loaded purpose and defaults; efficient but could be slightly more structured. No wasted words.

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?

Given 14 optional parameters and no output schema, the description covers modes, defaults, and post-action guidance. Lacks return format details, but rule says output schema not required. Adequate for a list tool.

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?

With 100% schema coverage, the description adds value by explaining how parameters activate different modes (e.g., any of task_type/stack/min_confidence_* triggers constraint-solver mode). Clarifies parameter interaction beyond individual descriptions.

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 it lists entities in the NaN Mesh trust network, specifies default sorting and constraint-solver mode, and distinguishes from sibling tools by mentioning post-browsing actions with nanmesh.trust.review or nanmesh.trust.favor.

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?

Provides clear context for default vs constraint-solver modes and directs to sibling tools for subsequent actions. Does not explicitly state when not to use, but the guidance is sufficient.

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