Skip to main content
Glama
Sign In
Andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Ask an Andru specialist

consult_agent

Get a domain-scoped answer from an Andru expert for open questions that no other tool fits; choose a module, pass history to continue, and check the quote first because calls are paid.

Instructions

Any step, when no other tool fits: use this when the person asks an open question for one of Andru's domain experts. Gets a domain-scoped answer in natural language (it may call lookup tools; tools that cost money must be called directly). One turn per call; pass prior turns as history to continue. Use module to pick the expert (e.g. 'market-clarity', 'deal-acceleration', 'due-diligence', 'portfolio-ops'). Paid. Check the price with quote before running.

Input Schema

NameRequiredDescriptionDefault
moduleYesWhich domain agent to consult (e.g. 'market-clarity', 'due-diligence', 'portfolio-ops').
historyNoOptional prior turns: [{ role, content }]. At most 10 turns of 2,000 characters each.
messageYesYour question / request for the agent (up to 4,000 characters).
quoteIdNoOptional: the quote_id from quote, to pay the quoted price (held for 30 minutes).
idempotencyKeyNoOptional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.
maxAmountCentsNoOptional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.9
    • addedInput schema / properties / idempotencyKey
      Added value: +{
+  "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.",
+  "type": "string"
+}
    • addedInput schema / properties / maxAmountCents
      Added value: +{
+  "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / quoteId
      Added value: +{
+  "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).",
+  "type": "string"
+}
  2. Addedv1.4.1

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the call is paid, it may itself invoke lookup tools, it is single-turn so continuation requires passing `history`, and cost control flows through quote/quoteId/maxAmountCents. These are non-obvious behavioral traits for a read-ish, open-world, paid tool that the readOnlyHint=false and openWorldHint=true flags only hint at.

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?

Dense but front-loaded: routing rule, then behavior, then parameters, then cost warning. Nearly every clause earns its place; the only weak spot is the opening 'Any step,' fragment, which is less informative than what follows.

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

Completeness5/5

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

No output schema, yet the description says the return is a natural-language domain-scoped answer, covers the fallback-tool role, conversation continuation, and the payment/quote flow. That is everything an agent needs to invoke it safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description goes above it by explaining the conversational model ('one turn per call; pass prior turns as history to continue') and giving module values that map the abstract expert router to concrete domains. It doesn't re-explain quoteId/idempotencyKey, but the schema already does that well.

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: routes an open question to a named domain expert and returns a natural-language answer. It distinguishes itself from concrete siblings by naming module values ('market-clarity', 'deal-acceleration'), though the opening phrase 'Any step, when no other tool fits' is a bit diffuse before the concrete statement arrives.

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

Usage Guidelines5/5

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

Explicit routing rule ('when no other tool fits', 'the person asks an open question for one of Andru's domain experts'), explicit constraint (tools that cost money must be called directly, not via the agent), and explicit prerequisite (check price with quote before running). An agent knows exactly when and when not to use it.

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