Skip to main content
Glama
Sign In
nc-mcp-server

nc-mcp-server

by cloud-py-api
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_question

Read-onlyIdempotent

Get a single question from a form by providing numeric form and question IDs. Returns the full question definition, including options.

Instructions

Get a single question including its options.

Args: form_id: Numeric form id. question_id: Numeric question id.

Returns: JSON object with the question's full definition.

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": {
      "form_id": "<form_id>",
      "question_id": "<question_id>"
    },
    "name": "get_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
form_idYes
question_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent. The description adds that the response includes options and the full definition, providing useful context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and well-structured with a clear header, args, and returns sections. No superfluous text.

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 a simple get operation with two parameters and an output schema, the description is complete. It states the return type and scope.

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 0%, so the description's parameter explanations are essential. It clarifies that form_id and question_id are numeric identifiers, giving semantic meaning beyond the integer type.

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?

States a specific verb (get) and resource (single question) and notes that options are included. Clearly distinct from list_questions which lists multiple questions.

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

Usage Guidelines3/5

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

Does not explicitly state when to use this vs alternatives like list_questions. It implies usage when a single question is needed, but no exclusions or alternatives are mentioned.

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