Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_company

Read-only

Retrieves the account company profile, including legal name, registration code, country, EU VAT number, billing address and email, plus VAT VIES check status, so you can confirm saved billing details.

Instructions

Get the account company profile: legal name, registration code, country, EU VAT number, billing address and billing email, with the state of the VAT number VIES check. company is null before one is saved. Needs settings:read on an account-wide key; a key bound to one sub-account is refused account_key_required, since this is the account itself. The owner edits it in the dashboard on the Billing page (https://proof.holdings/billing).

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
companyNoNull until the owner saves one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses authorization scope, the exact error name for sub-account keys, and the null-company state before a profile is saved. It also states the auth prerequisite (PROOF_API_KEY + restart) and that start_login will not satisfy it, which is precisely the kind of context annotations cannot carry.

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?

The field list is front-loaded, followed by the permission constraint and then the access note, which is a sensible ordering. The ACCESS paragraph is somewhat boilerplate (setup instructions) but is genuinely actionable for a first call, so little is wasted.

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?

With an output schema present, return values need not be explained, and the description still covers permissions, the failure mode, the empty state, and where the data is edited. Nothing an agent needs in order to call this successfully or interpret a refusal is missing.

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 is 4; there is nothing for the description to clarify about inputs. The description correctly spends no words on parameter semantics and instead covers return-state and access behavior.

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 opens with a specific verb and resource ("Get the account company profile") and enumerates the exact fields returned, including the VIES check state. It implicitly distinguishes itself from personal-profile siblings like get_profile/get_my_profile by stressing "account company profile," though it never names an alternative explicitly.

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 conditions: settings:read is required on an account-wide key, and a sub-account-bound key is refused with account_key_required. It also points to the dashboard Billing page for edits and clarifies that start_login does not unlock this tool, which is a useful exclusion even though no sibling is offered as an alternative read path.

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

Deploy Server

Other Tools