Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Get briefing answers

get_briefing
Read-only

Retrieve a project's flattened briefing answers as JSON, optionally scoped to an organization, to access research briefing data.

Instructions

Read flattened briefing answers JSON for a project.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the bar is lower. The description contributes the term "flattened", a small but genuine hint about output shape. It says nothing about behavior when a project has no submitted briefing, or about required access to the project/org.

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?

A single front-loaded sentence with zero filler, and the scope ("for a project") lands immediately. It is efficient but so terse that it borders on under-specification rather than optimal density.

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 simple two-parameter read-only getter with no output schema, the essentials are present but thin: "flattened" is unexplained, and the agent gets no sense of the returned structure or empty-state behavior. Adequate as a minimum viable definition, not complete.

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 coverage is 50%: organization is well documented in the schema while project_id is not. The description's "for a project" loosely reinforces project_id but adds no format, type, or lookup semantics beyond that, so it neither compensates for nor worsens the gap.

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?

States a concrete verb and resource ("Read flattened briefing answers JSON") scoped to a project, which an agent can distinguish from the write-side sibling submit_briefing_answers. It stops short of explicitly naming that sibling or the related get_project, so the differentiation is implied rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the alternative submit_briefing_answers or get_project. The only signal is the verb "Read", which restates the read-only nature rather than routing the agent among alternatives.

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