Skip to main content
Glama

Get company context

get_company_context
Read-onlyIdempotent

Retrieves the current company user’s B2B role, permissions, customer group, shared catalogue, credit and payment status, and sales rep so agents can scope actions correctly.

Instructions

Who you are acting for: company, user role and B2B permissions, customer group, shared catalogue, credit limit and available credit (if the user may see it), payment-on-account status and assigned sales rep. Call this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structural behavior: credit limit and available credit are returned only 'if the user may see it', disclosing that output is permission-filtered and that an agent should not assume those fields are always present. It does not describe the failure path or what happens when identity cannot be resolved.

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?

Two sentences, no filler, and every clause in the first sentence names a distinct data element rather than padding. The one structural weakness is that the single most actionable instruction, 'Call this first', is buried at the very end instead of being front-loaded.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it does so by listing the returned context fields plus the conditional-visibility caveat on credit. For a zero-parameter, read-only context tool that is close to sufficient; only error/prerequisite behavior (e.g., what an unauthenticated or unrecognized caller gets) is left unaddressed.

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 the baseline of 4 applies and there is nothing for the description to disambiguate. The enumerated fields in the description instead function as return-value documentation, which is a bonus rather than a parameter 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?

The definition names a specific resource — the acting identity/company context — and enumerates exactly what it surfaces (company, role and B2B permissions, customer group, catalogue, credit, payment-on-account status, sales rep). That is concrete enough to separate it from siblings like get_customer_price or get_product. It stops short of a crisp verb+resource opening sentence ('Who you are acting for:' is descriptive framing rather than 'Returns the identity...'), but the content is unambiguous.

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?

'Call this first' is an explicit ordering directive that tells the agent exactly when in a workflow this tool belongs, which is the main guidance an agent needs for a zero-parameter context tool. There is no statement of alternatives or when not to call it, and no note on what to do if the call is unavailable, so it does not reach the 5 bar.

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