Skip to main content
Glama

get_company_overview

Read-onlyIdempotent

Read one company's ISMS work in ISMS Copilot: the stages of its engagement map (Build, Run, Audit) with status and due date, how many findings wait for a decision, recent decisions, and its documents with the ids start_review takes. Call it after the person names a company (company_id from list_companies) and before you start a review. Decisions are made by the person in ISMS Copilot (app_url). Requires workflows:read.

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": {
      "company_id": "<company_id>"
    },
    "name": "get_company_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesThe company (a UUID from list_companies)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower; the description still adds real context by stating that decisions are made by the person in ISMS Copilot (app_url), i.e. this tool surfaces but does not act on findings. It also discloses the required workflows:read permission, which annotations do not carry. Response size or pagination behavior for large document lists is not addressed, keeping it shy of a 5.

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?

Content is front-loaded with the resource and its payload, followed by call ordering, ownership of decisions, and the permission requirement — a sensible progression with no filler sentences. It is fairly dense in a single paragraph, but each clause carries distinct information an agent needs.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description enumerates the salient return contents, states the prerequisite id source, the call ordering, and the auth scope. Nothing material needed to invoke it correctly appears to be missing.

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?

The single parameter is fully described in the schema ("The company (a UUID from list_companies)"), and the description's phrase "company_id from list_companies" merely repeats that provenance rather than adding format or validation detail. With 100% schema coverage and one parameter, the baseline of 3 is the right ceiling.

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 opens with a specific verb and resource ("Read one company's ISMS work") and then enumerates exactly what comes back: engagement map stages (Build, Run, Audit) with status and due date, pending-finding counts, recent decisions, and documents with the ids start_review consumes. This is far more than a restatement of the name and lets an agent distinguish it from get_company or get_company_context by content.

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 concrete sequencing rules: call it after the person names a company (with company_id sourced from list_companies) and before starting a review. That is clear when-to-use guidance. It does not explicitly exclude the similarly named siblings (get_company, get_company_context), so an agent comparing those must infer the difference from purpose alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.