hub-equity-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_entity_profile

Read-onlyIdempotent

Retrieve a company profile with identifiers, sector, auditor, employee count, legal form, fiscal year end, and recent filings summary to provide context after finding an entity.

Instructions

Comprehensive company snapshot: identifiers, sector, auditor, employees, legal form, fiscal year end, recent filings summary.

Use after find_entity when the user wants context, or as a first call when the user asks 'tell me about ' / 'qui est '.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_entity_profile"
  }
}

Input Schema

Name	Required	Description	Default
`entity_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 19, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered. The description adds the content scope of the response, but that largely duplicates the output schema, and it says nothing about cost, latency, or freshness of the snapshot.

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?

Front-loads the payload summary, then the routing guidance, in two tight sentences. No filler and no repetition of annotation or schema content.

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 an output schema present, return values need not be re-explained, and usage guidance is strong. The remaining gap is the undocumented entity_id contract, which is the only input an agent must supply and is not clarified anywhere.

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?

There is one required parameter (entity_id) with 0% schema description coverage, so the description carries the burden. It only indirectly implies the ID source by saying to call this after find_entity; it never states the expected format or origin of entity_id explicitly.

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?

States a specific verb and resource ('company snapshot') and enumerates the exact payload (identifiers, sector, auditor, employees, legal form, fiscal year end, recent filings summary). This clearly separates it from siblings like find_entity (search) and get_fact (single metric).

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?

Gives concrete sequencing ('Use after find_entity') plus trigger phrases for direct invocation, including a French variant. It names one alternative, but does not state when NOT to use it (e.g. for a single datapoint, use get_fact), so it stops short of full when/when-not coverage.

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