Skip to main content
Glama
Sign In

Apideck MCP

by dev.apideck.mcp
OverviewDiscussionsAdmin

list_tools

Read-onlyIdempotent

Discover Apideck tools. Call with no args for domain index; filter with domain/search_terms/scope. Scoped to the connection's supported resources when service_id is set.

Input Schema

NameRequiredDescriptionDefault
scopeNoFilter by mutation scope: "read" (no writes), "write" (creates/updates), or "destructive" (deletes/overwrites). Omit to include all scopes.
domainNoRestrict results to a single tool domain (e.g. "accounting", "hris"). Omit to get the cross-domain index. Use a key returned by a prior no-arg call.
search_termsNoCase-insensitive substring terms ANDed across a tool name/description (e.g. ["invoice","create"]). Omit to list everything in the domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / domain / description
      Added value: +"Restrict results to a single tool domain (e.g. \"accounting\", \"hris\"). Omit to get the cross-domain index. Use a key returned by a prior no-arg call."
    • addedInput schema / properties / scope / description
      Added value: +"Filter by mutation scope: \"read\" (no writes), \"write\" (creates/updates), or \"destructive\" (deletes/overwrites). Omit to include all scopes."
    • addedInput schema / properties / search_terms / description
      Added value: +"Case-insensitive substring terms ANDed across a tool name/description (e.g. [\"invoice\",\"create\"]). Omit to list everything in the domain."
    • addedInput schema / required
      Added value: +[]
  2. Changed3 schema fields changed
    • addedInput schema / properties / domain
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "enum": [
+    "read",
+    "write",
+    "destructive"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / search_terms / description
      Removed value: -"Filter the list of tools.\nEach term is matched case-insensitively as a substring against tool name, description, and scopes.\nMultiple terms are combined with a logical OR: a tool is included if ANY term matches ANY field.\nIf not provided, all tools are returned."
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds the no-arg default behavior and the connection-scoping constraint, but the per-filter semantics it describes are already spelled out in the schema property descriptions.

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?

Two short sentences, zero filler, and the default no-arg behavior is front-loaded before the filtering options. Every clause carries information.

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 3-param, no-output-schema discovery tool with full annotation coverage, this is nearly sufficient: the entry mode, filters, and connection scoping are all stated. The mention of service_id, which is not an input parameter, introduces mild ambiguity about whether it must be supplied or is inferred from the connection.

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 description coverage is 100% and the enum on scope is documented in-schema, so the schema does the heavy lifting. The description only echoes the parameter names in one clause without adding format or interaction detail (e.g., how search_terms combine with domain).

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?

States a specific verb and resource ("Discover Apideck tools") and immediately clarifies the two modes: no-arg domain index vs. filtered listing. It is distinguishable from siblings like describe_tool_input and execute_tool, though it never names them explicitly.

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?

Gives concrete usage branching: no args for the domain index, domain/search_terms/scope to filter, and notes result scoping when service_id is set. Clear context, but no explicit exclusions or pointers to sibling tools for the follow-up steps (describe/execute).

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

All Apideck MCP toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources