Granoflow MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

granoflow_api_request

Send HTTP requests to Granoflow's local API to manage tasks and projects. Use for operations not covered by dedicated tools.

Instructions

Run an allowed Granoflow Local HTTP API request. Prefer dedicated tools when available.

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": {
      "path": "<path>"
    },
    "name": "granoflow_api_request"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`input`	No	JSON object sent to the Granoflow Local HTTP API.
`dryRun`	No	When true, previews write requests.
`method`	No		GET

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 1, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, leaving the description to cover behavior. It only mentions 'allowed' without explaining what that means, and fails to disclose the default dry-run behavior (though present in schema). No mention of auth, side effects, or error handling.

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 a single concise sentence front-loaded with the action. No unnecessary wording, but brevity comes at the cost of completeness.

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

Completeness2/5

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

With 4 parameters, no output schema, and no annotations, the description is too minimal. It does not explain what endpoints are allowed, authentication, response format, or how to interpret results, leaving significant gaps for a generic HTTP tool.

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 50%, but the description adds no parameter-specific information beyond what is in the schema. The description does not compensate for the missing parameter 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?

Description clearly states the tool runs an allowed Granoflow Local HTTP API request and explicitly advises to prefer dedicated tools when available, distinguishing it from sibling tools.

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 explicit guidance to prefer dedicated tools, which helps the agent decide when to use this fallback tool. However, it lacks explicit when-not-to-use or prerequisites.

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