Skip to main content
Glama

Company Framework

Ask JD

ask_jd

Sends a question to JD Davenport, who wrote the Company Framework method. Includes an optional email address, which is the only way a reply can be sent.

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": {
      "question": "<question>"
    },
    "name": "ask_jd"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoWhere JD should reply. Optional, but without it there is no reply.
questionYesThe question, in the person's words.

Output Schema

NameRequiredDescriptionDefault
messageYes
receivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, non-destructive, non-idempotent call; the description adds the genuinely useful behavior that the email field is the sole reply channel, which shapes whether to supply it. It does not say how the question is delivered (form, email, queue), expected turnaround, or that each call sends a separate message, which are the remaining unknowns for a message-sending tool.

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, recipient and purpose front-loaded, with the consequential detail about the reply channel second. Nothing is padded and no sentence is wasted.

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?

With an output schema present and full parameter coverage, the description needn't explain return values. It covers what the tool does and the key input consequence; only delivery mechanics and expected response timing are absent, which are minor for a two-parameter tool.

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%, so both parameters are already documented, including the fact that email is optional but required for a reply. The description restates that same constraint without adding format, validation, or default details, so the baseline of 3 applies.

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?

"Sends a question to JD Davenport" gives a concrete verb+recipient and names who JD is (author of the Company Framework method), which distinguishes it from lookup-style siblings like search_company_framework. It stops short of explicitly stating that this routes to a human rather than a database, but the action is unambiguous.

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?

Usage is only implied: an agent can infer you call this when you want a question answered by JD rather than searched for. There is no explicit when-to-use / when-not-to-use guidance and no mention of alternatives such as searching the framework first, so the agent must infer routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources