Skip to main content
Glama

Request a call with a human expert

request_expert_review
Read-only

Use this only when the user asks for it in their own words: they want to talk to a person, ask for a human expert, or ask how to get in touch about their situation. Never call it on your own initiative, never as a closing suggestion, and never because an answer seems uncertain. It returns a link to book a 30 minute introductory call with Zahed Ashkara, an independent AI and privacy consultant behind Praxikon. Send no part of the conversation: the tool takes only a language and, optionally, a topic from a fixed list, and nothing about the user. Show the title, the sentence and the link to the user as they are, and let the user decide whether to book.

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": "request_expert_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the text and of the booking page. Dutch is the default.nl
topicNoOptional subject of the question, from this fixed list only. It travels in the link as a campaign label (utm_content) to the booking page, so the booking can be traced to this tool. It is the only thing from the conversation that does; it names no person.
store_for_improvementNoOptional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; only the anonymous daily count remains. See https://www.praxikon.com/nl/legal/privacy, section 2.7.

Output Schema

NameRequiredDescriptionDefault
urlYes
langYes
noteNo
textYes
titleYes
topicNo
provenanceYes
duration_minutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / store_for_improvement / description
      Previous value: -"Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; nothing of this call is then kept beyond the anonymous daily count. See https://www.praxikon.com/nl/legal/privacy, section 2.7."New value: +"Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; only the anonymous daily count remains. See https://www.praxikon.com/nl/legal/privacy, section 2.7."
  2. Changed1 schema field changed
    • addedInput schema / properties / store_for_improvement
      Added value: +{
      +  "default": true,
      +  "description": "Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; nothing of this call is then kept beyond the anonymous daily count. See https://www.praxikon.com/nl/legal/privacy, section 2.7.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces that by promising only a link is returned. It adds real behavioral context beyond the annotations: no part of the conversation is transmitted, only a language plus an optional fixed-list topic travels, and the user must be shown the title/sentence/link verbatim and decide for themselves. The mild tension between a link to an external booking page and openWorldHint=false is resolvable (the tool generates a static URL rather than fetching external data), so it is not a contradiction.

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?

Front-loaded with the most decision-critical rule (only on explicit user request), then the exclusions, then return behavior and privacy. Every sentence carries weight, but the single dense paragraph mixes usage rules, return format, and data-handling policy; light structuring would improve scanability without adding length.

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?

An output schema exists, yet the description still tells the agent what the response means (a booking link) and how to present it to the user, which is the operationally important part. Combined with the zero-required-parameter design and the explicit data-minimization statement, an agent has everything needed to call this correctly and present it safely.

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 the baseline is 3, but the description adds privacy-relevant meaning the schema alone does not: 'takes only a language and, optionally, a topic from a fixed list, and nothing about the user.' The utm_content purpose of topic is also documented in the schema itself. The only parameter not echoed in the description is store_for_improvement, which the schema documents thoroughly with a privacy link.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('request a call with a human expert') and then concretizes it: it returns a booking link for a 30 minute introductory call with Zahed Ashkara of Praxikon. The sibling tools are all informational (answer_question, check_case, get_applicable_obligations), so the escalation-to-human framing makes the distinction unmistakable.

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 when-to-use ('only when the user asks for it in their own words: they want to talk to a person, ask for a human expert...') and three explicit when-not rules: never on own initiative, never as a closing suggestion, never because an answer seems uncertain. This directly pre-empts the most likely misuse pattern for a handoff tool.

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