Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

List panel projects / demands

list_panel_projects
Read-only

List Cint, Bilendi, and Dynata panel demands, audits, projects, or target groups for admin users; a 403 means permission denied, not an empty result.

Instructions

List Cint demands or audit, Bilendi projects or audit, or Dynata projects or audit. These routes require a deeptrue admin. A 403 is an admin refusal, not an empty list.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
providerNo
resourceNoPanel resource the deeptrue API exposes for this provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.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=true, so safety is covered. The description adds genuinely non-obvious behavior: an admin authorization gate and the interpretation that a 403 is an admin refusal rather than an empty result — a distinction that would otherwise cause an agent to report false negatives.

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?

Three short sentences, with the resource/provider mapping front-loaded and the failure-mode caveat last. The middle provider list is dense but every clause carries information; nothing is padded.

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

Completeness3/5

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

For a read-only, four-parameter listing tool with no output schema and low schema coverage, the definition covers authorization and error interpretation but leaves out pagination behavior, return shape, and one valid resource value. Adequate but with clear gaps.

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 only 25% (only 'resource' is documented), so the description needs to compensate. It does usefully tie provider values to valid resource combinations, but it skips 'target-groups' entirely and says nothing about limit/offset pagination semantics.

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?

The description uses a specific verb ('List') with concrete resources enumerated per provider ('Cint demands or audit, Bilendi projects or audit, or Dynata projects or audit'), which makes it distinguishable from the sibling list_projects. It never explicitly contrasts itself with list_projects, and it omits the 'target-groups' resource that the schema allows, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the provider enumeration (this is the panel-side listing route), and a prerequisite is supplied ('These routes require a deeptrue admin'). However, there is no explicit when-to-use-versus-alternative statement telling an agent to pick this over list_projects or list_organizations.

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