Praxikon

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.

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the text and of the booking page. Dutch is the default.	nl
`topic`	No	Optional 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_improvement`	No	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.

Output Schema

Name	Required	Description	Default
`url`	Yes
`lang`	Yes
`note`	No
`text`	Yes
`title`	Yes
`topic`	No
`provenance`	Yes
`duration_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

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"
+}

First observedOct 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past the annotations: it discloses the return value (a booking link), the human on the other end, and a privacy contract — no conversation content is sent, only a language and an optional fixed-list topic, with an opt-out via store_for_improvement. It also instructs that the title/sentence/link be shown verbatim rather than paraphrased. No contradiction with readOnlyHint=true or openWorldHint=false; producing a URL is not an external interaction.

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 gating condition before any mechanics, and each sentence carries a distinct duty (trigger, prohibitions, return value, data handling, presentation). Slightly dense in the final sentence about showing title/sentence/link, but nothing is padding.

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?

Even though an output schema exists, the description supplies the non-obvious essentials an agent needs: who the call is with, that contact data is never transmitted, and how to present the result. Nothing required for correct, safe invocation is missing.

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 schema already documents lang, topic and store_for_improvement in detail, and the baseline would be 3. The description adds the framing that matters for correct invocation — 'the tool takes only a language and, optionally, a topic from a fixed list, and nothing about the user' — which reinforces the enum constraint and the data-minimisation rule rather than duplicating field text.

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+resource (request a call with a human expert) and immediately specifies what the tool actually produces: a booking link for a 30-minute introductory call with a named consultant. The action is unmistakably distinct from analytical siblings like answer_question or classify_system.

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?

Gives the positive trigger (only when the user asks in their own words to talk to a person / get in touch) and three explicit prohibitions: never on own initiative, never as a closing suggestion, never because an answer seems uncertain. It also hands the final decision to the user, which resolves the follow-up ambiguity an agent would otherwise have.

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

All Praxikon tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?