Skip to main content
Glama
Sign In
intakeq-mcp

intakeq-mcp

by oktopeak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

set_api_key

Store your IntakeQ API key to authenticate and verify connectivity with the IntakeQ server.

Instructions

Store your IntakeQ API key and verify connectivity

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": "set_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesIntakeQ API key from Settings → Integrations → Developer API

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It states two key behaviors (storing the key and verifying connectivity), but does not mention side effects like overwriting an existing key, persistence, or error handling, leaving some uncertainty.

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 a single, front-loaded sentence that directly states the tool's core function without superfluous words or repetition.

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 configuration tool with one parameter and full schema coverage, the description provides sufficient context including the connectivity check. It doesn't detail return values, but the absence of an output schema makes that acceptable.

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?

The schema description for the single parameter (api_key) is explicit and includes where to find the key, achieving 100% coverage. The tool description adds no additional parameter semantics, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as storing an IntakeQ API key and verifying connectivity, using specific verbs and a resource. It implicitly distinguishes from sibling tools like auth_status and clear_api_key, though it doesn't explicitly differentiate them.

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 purpose is clear enough that an agent can infer when to use it (when setting up or updating the API key), but there is no explicit guidance about when not to use it or when to prefer alternatives like auth_status or clear_api_key.

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