Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

List organizations

list_organizations
Read-only

Lists organizations available to the authenticated DeepTrue user, helping you select the correct organization context before managing projects or briefings.

Instructions

List organizations available to the authenticated DeepTrue user. Use when choosing an org context.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful scoping fact that results are limited to orgs the caller can access, but says nothing about result shape, ordering, or whether an empty list is possible. With annotations carrying the safety profile, this is an adequate but modest addition.

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?

Two short sentences, zero filler, with the purpose stated first and the usage cue second. Nothing could be removed without losing information.

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 no-parameter read tool whose annotations declare its safety profile, the description covers what it returns at a high level (organizations for the current user) and when to call it. The one gap is that it does not indicate what identifying field comes back, which an agent needs to pick an org for set_active_organization; with no output schema, that detail must be discovered at call time.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain and the baseline of 4 applies.

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 gives a specific verb and resource ("List organizations") plus a scope qualifier ("available to the authenticated DeepTrue user"), which separates it from the singular get_organization and the mutating set_active_organization. It does not explicitly name those siblings, keeping it just 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 Guidelines4/5

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

"Use when choosing an org context" gives a concrete triggering situation rather than a generic restatement. It stops short of naming the follow-up tool (set_active_organization) or stating exclusions, so it is clear context without explicit alternatives.

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