Derrick App

Official

by DerrickAppOrg

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Configure Derrick API key

derrick_configure

Idempotent

Save your Derrick API key locally to authenticate and enable B2B enrichment workflows.

Instructions

Save your Derrick API key locally. To get your key: install the Derrick Google Sheets extension (https://derrick-app.com), open a sheet > Derrick menu > burger icon > API. Requires Standard plan (€20/mo) or above.

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": {
      "api_key": "<api_key>"
    },
    "name": "derrick_configure"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	Yes	Your Derrick API key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 21, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Description 'Save ... locally' is consistent with idempotentHint=true. Adds plan requirement but does not elaborate on side effects or beyond 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?

Three sentences, front-loaded with main action, no unnecessary words.

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?

For a simple configuration tool with one parameter and annotations, the description covers purpose, obtaining key, and prerequisite adequately.

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 covers 100% with basic description. Description adds value by specifying where to obtain the key and the required plan.

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?

Clearly states verb 'save' and resource 'Derrick API key locally'. Distinguished from siblings as the only configuration tool.

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 instructions on obtaining the key and prerequisite plan. Implicitly indicates this must be used before other Derrick tools.

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