Gripp MCP

gripp_call

Call any Gripp API method by specifying its full method name. For methods that modify data, pass confirm=true to prevent unintended changes.

Instructions

Call any Gripp API method by full method name. Non-read methods require confirm=true.

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": {
      "method": "<method>"
    },
    "name": "gripp_call"
  }
}

Input Schema

Name	Required	Description
`method`	Yes	Full Gripp method name, for example company.getCompanyByCOC or file.getContent.
`params`	No	Positional JSON-RPC params for the Gripp method.
`confirm`	No	Required for methods that may modify Gripp data.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions the confirm requirement but does not disclose other traits like error handling, rate limits, or whether read-only methods are safe. The description does not contradict annotations (since none exist) but is insufficient.

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?

The description is two sentences, front-loaded with the main action, and contains no unnecessary words. It is concise and direct.

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?

For a generic caller tool with no output schema, the description lacks details on return format, usage examples, or how to construct method names. The pattern is in schema but not in description, and there is no mention of error handling or authentication. This leaves gaps for an AI agent to use it effectively.

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

Parameters3/5

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

Schema coverage is 100% and already describes all parameters (method, params, confirm). The description adds the statement about non-read methods requiring confirm, which echoes the schema's confirm description but provides minimal extra meaning. Baseline 3 is appropriate.

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 what the tool does: calls any Gripp API method by full method name. It also specifies the requirement for confirm on non-read methods, which distinguishes it from sibling tools that handle specific CRUD operations.

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?

The description gives a key usage requirement ('Non-read methods require confirm=true') but does not explicitly guide when to use this tool versus siblings like gripp_get or gripp_create. The use of 'any' implies a generic fallback, but this is not stated directly.

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

Deploy Server