Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Check organization

set_active_organization
Read-only

Validates that the current user can access a specified organization, so later calls can target it via the organization parameter, X-DeepTrue-Org header, or DEEPTRUE_ORG environment variable.

Instructions

Validate that the user can use an organization. Does not persist across stateless HTTP requests. Pass organization on later tools or send X-DeepTrue-Org / DEEPTRUE_ORG.

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": {
      "organization": "<organization>"
    },
    "name": "set_active_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationYesOrganization domain/slug (URL org name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint=true and openWorldHint=false annotations, the description discloses the key non-obvious trait: the call is stateless and does not carry forward. It also names the two propagation mechanisms (parameter on later tools, or header/env var). It does not say what happens on an invalid or unauthorized organization, which would complete the picture.

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 core claim front-loaded and the stateless caveat immediately after. The final sentence is terse to the point of being clipped ('Pass organization on later tools or send X-DeepTrue-Org / DEEPTRUE_ORG'), but nothing is wasted.

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 single-parameter, read-only tool with no output schema, the description covers what matters: that it validates access and that the effect is not sticky. The remaining gap is error/return behavior on an invalid organization, which is minor given the annotation already marks this as a safe read.

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 100% and the single parameter already documents itself as 'Organization domain/slug (URL org name)', so the baseline is 3. The description adds only indirect context about the organization identifier via the header names, not new syntax or format detail.

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 states a specific verb and resource: 'Validate that the user can use an organization.' It effectively resolves the tension between the tool name ('set_active_organization') and title ('Check organization') by clarifying that this is a validation/context check, not a persisted state change. It does not, however, distinguish itself from siblings like get_organization or list_organizations.

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?

It gives actionable usage context: the result does not persist across stateless HTTP requests, so the organization must be re-supplied on later tools or via the X-DeepTrue-Org header / DEEPTRUE_ORG variable. This tells an agent how to use the outcome rather than just what the tool does. It stops short of naming an explicit alternative tool or a when-not-to-use condition.

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