Skip to main content
Glama

Arquestra Consulting Market Radar

Panel usage (internal)

panel_event
Read-onlyIdempotent

Internal to the radar's panel (MCP App), hidden from the model: counts which part of the panel the person opened. Returns no data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "part": "<part>"
    },
    "name": "panel_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNoLeave this out. Set only by the radar's panel (MCP App) when the person uses its filters or 'show more' (panel), or by the site owner's own tests (dev), so that use is counted apart.
partYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior1/5

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

The description says the tool 'counts' panel openings, which implies a state-changing event-recording operation and repeated calls incrementing a counter. That conflicts with the annotations readOnlyHint=true and idempotentHint=true, which promise no environment modification and no additional effect on repeated calls.

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?

The description is two concise sentences with the internal scope and zero-data return stated up front. Every sentence carries useful information and there is no filler.

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 simple internal telemetry tool, the description covers purpose, audience restriction, and return behavior, including that no data is returned. The remaining gap is the unexplained `part` enum values, though the schema supplies the allowed values.

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?

The description adds meaning for `part` by saying it identifies which part of the panel was opened, but it does not explain the `bid`, `more`, and `alert` enum values. The `via` parameter is well documented in the schema, while the 50% schema description coverage leaves one parameter without schema-level detail.

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?

The description states a specific action and scope: it counts which part of the radar's panel a person opened and returns no data. This clearly distinguishes it from the sibling tools, which retrieve firm, market, or tender data.

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?

The description explicitly says the tool is internal to the radar's panel and hidden from the model, which is a clear when-not-to-use instruction for the agent. The schema further clarifies that `via` should be left out by the model and is set only by the panel or site-owner tests.

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