Gripp MCP

gripp_getone

Retrieve a single entity from Gripp by specifying the entity type and filters. Returns the first matching item.

Instructions

Retrieve a single Gripp entity. Uses the entity.getone API method and returns the first matching item.

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": {
      "entity": "<entity>"
    },
    "name": "gripp_getone"
  }
}

Input Schema

Name	Required	Description	Default
`entity`	Yes	Gripp entity name, for example company or invoice.
`filters`	No	Gripp filters. Use full field names like company.id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 30, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must fully cover behavior. It mentions using the entity.getone API method and returning the first match, but lacks details on side effects (read-only nature), authorization needs, or rate limits.

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 concise, consisting of two sentences with no unnecessary words, efficiently conveying the core functionality.

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?

For a simple retrieval tool with no output schema, the description adequately explains the action and result (first matching item). Additional context like examples could improve completeness, but it is largely sufficient.

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%, with both parameters having descriptions. The description adds marginal value beyond the schema, stating it returns the first matching item, which relates to filters but does not provide new parameter-level insight.

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 the tool retrieves a single Gripp entity and returns the first matching item, distinguishing it from sibling tools like gripp_get which likely return multiple results.

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?

While the description implies usage for retrieving one item, it does not explicitly state when to use this tool over alternatives or provide any when-not guidance.

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

Deploy Server