Skip to main content
Glama

PariteCK

by com.entangleeq
OverviewDiscussionsAdmin

request_demo_lead

Use this when a user wants to be contacted by PariteCK, or asks for a demo, a quote or a meeting. This tool does NOT transmit contact details: it returns the URL of the PariteCK contact form, which the user must fill in themselves. Show them the returned URL. Never send a name, an email, a phone number or any personal data through this tool: PariteCK does not accept contact details relayed by an assistant, because the person's consent cannot be verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNameNoOptional. Company / organisation name, kept as an anonymous usage statistic. Never a person name.
primaryTopicNoOptional. Main interest: egapro | pay_gap | vss | csrd | global.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / companyName / description
      Previous value: -"Company / organisation name."New value: +"Optional. Company / organisation name, kept as an anonymous usage statistic. Never a person name."
    • removedInput schema / properties / contactName
      Removed value: -{
-  "description": "Name of the person to contact back.",
-  "maxLength": 100,
-  "minLength": 2,
-  "type": "string"
-}
    • removedInput schema / properties / email
      Removed value: -{
-  "description": "Professional email to reach the contact.",
-  "format": "email",
-  "maxLength": 150,
-  "type": "string"
-}
    • removedInput schema / properties / message
      Removed value: -{
-  "description": "Optional short context. No sensitive personal data, no salaries, no employee names.",
-  "maxLength": 1000,
-  "type": "string"
-}
    • changedInput schema / properties / primaryTopic / description
      Previous value: -"Main interest: egapro | pay_gap | vss | csrd | global."New value: +"Optional. Main interest: egapro | pay_gap | vss | csrd | global."
    • removedInput schema / properties / userConsent
      Removed value: -{
-  "const": true,
-  "description": "Must be true. Confirms the end user explicitly agreed to share these contact details with EntangleEQ.",
-  "type": "boolean"
-}
    • removedInput schema / required
      Removed value: -[
-  "companyName",
-  "contactName",
-  "email",
-  "userConsent"
-]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that no contact details are transmitted, that the return value is a URL the user must act on, and that PariteCK refuses assistant-relayed personal data for consent reasons. These are non-obvious behavioral constraints an agent could not infer.

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 trigger condition, then the return behavior, then the hard privacy constraint. Slightly repetitive in restating the no-personal-data rule twice, but the emphasis is defensible for a consent-critical instruction.

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?

For a two-optional-param tool with no output schema and no annotations, the description covers trigger, return value, and the critical restriction. Nothing an agent needs in order to call it correctly is missing.

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% and both parameters are optional and fully documented in the schema, so the baseline is 3. The description adds no parameter-level detail beyond what the schema already says (companyName as anonymous stat, primaryTopic enum).

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 action (returns the URL of the PariteCK contact form) triggered by a recognizable user intent (wants a demo, quote, meeting, or to be contacted). An agent can distinguish this from siblings like assess_readiness or search without opening any schema.

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 (user asks for a demo, quote, meeting, or contact) and explicit when-not / how-to-behave (never relay personal data, show the URL and let the user fill the form). The alternative behavior is spelled out rather than inferred.

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

All PariteCK toolsInspect
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