Skip to main content
Glama
Sign In
DuckPond MCP Server

DuckPond MCP Server

by jordanburke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

isAttached

Check whether a user's database is cached in memory to verify availability for queries.

Instructions

Check if a user's database is currently cached in memory

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "isAttached"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdNoUser identifier (optional if DUCKPOND_DEFAULT_USER is set)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.4.4

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must bear the full burden. It indicates a read-only check (no side effects), which is appropriate. However, it does not disclose error conditions, authentication requirements, or the meaning of 'cached'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently communicates the tool's purpose. It is appropriately sized for a simple check operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks information about the return value (expected to be boolean) and error handling (e.g., if user not found or default user used). Given the simplicity, it is moderately complete but could be enhanced.

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 input schema covers 100% of parameters with a description for 'userId'. The tool description adds no extra context beyond what the schema already provides, so a baseline score of 3 is warranted.

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 states the action ('check') and the resource ('user's database cached in memory'). It effectively distinguishes from sibling tools like 'detachUser' and 'execute' by implying a read-only query, though it could be more explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., 'detachUser' or 'listUsers'). The agent is left to infer usage context from the name and siblings.

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