Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_get_entry

Read-onlyIdempotent

Fetch a single Nexterm entry using its ID to inspect stored server connection details and configuration.

Instructions

Get one Nexterm entry by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>"
    },
    "name": "nexterm_get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the full safety profile of this call. The description adds nothing beyond that: no mention of behavior for missing IDs, error semantics, or whether the entry is returned with tags/folders expanded.

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?

A single front-loaded sentence with zero filler and the scoping mechanism ('by ID') placed immediately. It is efficient, though the brevity is under-specification rather than deliberate restraint.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, the safety profile is covered by annotations and return shape need not be described. Still missing is what a 'Nexterm entry' actually is relative to sources, identities and folders, which the surrounding sibling set makes ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% on the single parameter, so the description must carry the load. 'By ID' only restates the parameter name entry_id; it does not say what an entry ID is, where to obtain one (list_entries?), or that IDs are positive integers.

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?

States a specific verb and resource ('Get one Nexterm entry by ID'), so an agent knows this is single-item retrieval. It does not distinguish itself explicitly from the many sibling reads (nexterm_list_entries, nexterm_recent_entries, nexterm_get_source), leaving the singular 'one ... by ID' as the only differentiator.

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

Usage Guidelines2/5

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

No guidance on when to use this versus nexterm_list_entries or nexterm_recent_entries, and no prerequisites such as 'requires a known entry_id'. The only implied condition is that an ID must already be in hand, which is inferred rather than stated.

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