Skip to main content
Glama
stefanoamorelli

Companies House MCP Server

get_psc_individual_verification

Check the verification status of an individual PSC for a UK company by providing the company number and PSC ID.

Instructions

Get individual PSC verification state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
psc_idYesThe PSC ID
company_numberYesThe company number
Behavior2/5

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

Without annotations, the description must convey behavior. It only states 'Get individual PSC verification state', implying a read operation, but provides no details about the return value, error conditions, or what exactly 'verification state' means.

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 description is extremely concise (5 words) and front-loaded. While it could include more context, it avoids unnecessary verbosity for a simple two-parameter tool.

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?

Given the tool's many siblings and lack of output schema, the description is too brief. It does not explain how this tool differs from similar ones or what the verification state entails, leaving the agent underinformed.

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% with both parameters described in the schema. The description does not add additional meaning beyond the schema, so it meets the baseline of 3.

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 clearly states the verb 'Get' and the resource 'individual PSC verification state', which distinguishes it from other PSC tools like get_psc_individual or get_psc_individual_full_record. However, it does not explicitly explain why this tool is different from its siblings, so it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus the many sibling PSC tools. The description lacks any context about use cases or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stefanoamorelli/companies-house-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server