Switchbooks

Read Company Profile and Team

manage_company

Read-onlyIdempotent

Read the active company's profile, including its name, legal entity name, business description, and billing status. Use read for the profile or team to list members and pending invitations. These actions do not change company settings or team access. Set action to one of: read, team.

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

Input Schema

Name	Required	Description
`body`	No
`name`	No
`role`	No
`work`	No
`email`	No
`action`	No
`report`	No
`company`	No	Company for this call only: its ID, exact name, or a unique part of the name. Leave out to use the active company.
`compare`	No
`confirm`	No
`display`	No
`endDate`	No
`subject`	No
`delivery`	No
`lastName`	No
`agentName`	No
`companies`	No
`firstName`	No
`startDate`	No
`entityName`	No
`description`	No
`weeklyCheck`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The description reinforces the read-only nature of the tool, which is backed by annotations, and specifies the concrete types of data (name, billing status, members) returned. While the annotations cover safety, the description adds useful scope context.

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 definition is highly concise, front-loading the core function and immediately addressing the distinction between the 'read' and 'team' actions in two highly efficient sentences.

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

Completeness2/5

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

Despite clarifying the purpose, the tool remains functionally incomplete for an agent. With 22 parameters and no output schema, the description provides insufficient context on how complex inputs (like `report`, `compare`, or `weeklyCheck`) affect the read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite the vast number of parameters (22), the description only semantically clarifies 4-5 specific output data fields. Given that schema description coverage is extremely low (5%), the description fails to adequately explain the role of the numerous unused/unspecified input parameters.

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 clearly identifies the tool's function as reading company data (profile and team members) using specific data points like legal entity name and billing status.

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?

It provides explicit usage guidelines by telling the agent to use the 'read' action for profile information and the 'team' action for listing members. It also clarifies that the actions are non-mutating, preventing use as a replacement for mutation tools.

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

All Switchbooks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.