Skip to main content
Glama
Sign In
agenthouse-org

dealdesk-mcp

by agenthouse-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

dealdesk.discover

List DealDesk tool domains and unlock skill-gated tools for one domain; returns authorizedProjectIds to identify projects available for the current credentials.

Instructions

List additional DealDesk tool domains (desk, quotes, portfolio, directory, orders, admin) and unlock skill-gated tools for one domain. Also returns authorizedProjectIds. Prefer dealdesk.list_projects to list Connect projects.

Input Schema

NameRequiredDescriptionDefault
domainNoDomain to discover. Omit to list domains only.
projectIdNoDealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / projectId / description
      Previous value: -"DealDesk project id (must match API key / OAuth project)"New value: +"DealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects."
    • changedInput schema / required
      Previous value: -[
-  "projectId"
-]New value: +[]
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses a non-obvious side effect ('unlock skill-gated tools for one domain') and a return field ('authorizedProjectIds'), which is meaningful because this is not a pure read operation. However, it does not say whether unlocking is permanent, what permissions or skill gating are needed, or whether projectId selection affects the unlock.

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 tight clauses with zero filler, front-loaded with the primary action and followed by the secondary effect, the extra return field, and the sibling disambiguation. Every sentence earns its place.

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 two-parameter discovery tool with no annotations or output schema, the description covers the core action, the side effect, and one returned field. It is missing what the domain listing returns and the sequencing relationship to the gated domain tools it unlocks, which is the main remaining gap.

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 (domain, projectId) are already documented in the schema, including the omission semantics. The description adds only a partial domain enumeration and no extra syntax or behavioral detail beyond the schema, 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?

States a specific verb+resource ('List additional DealDesk tool domains') and adds a second function ('unlock skill-gated tools for one domain'). It enumerates most domains, though the list is incomplete versus the schema enum (omits portfolio-authoring and export), and it explicitly routes away from dealdesk.list_projects.

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 one explicit alternative and condition: 'Prefer dealdesk.list_projects to list Connect projects.' It implies the omission behavior for domain via the schema ('Omit to list domains only'), but never states when an agent should call discover at all (e.g., before invoking domain-gated tools).

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