CompanyGraph

fetch

One entity's page as written. Use to quote or display the source; for structured fields and references use get_entity. Input: id, from search, list_entities or any reference. Returns id, title, type, url and text, the Markdown source. Takes no name: search with match "name" finds the id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`type`	Yes
`model`	Yes
`title`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 21, 2026

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```
addedOutput schema / properties / id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / text
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / title
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / type
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / url

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "model"
-]New value: +[
+  "id",
+  "title",
+  "type",
+  "url",
+  "text",
+  "model"
+]

First observedSep 21, 2026

TDQS

A4.8/5.0

Behavior4/5

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

No annotations are present, so the description carries the behavioral burden. It discloses the return fields, that text is Markdown source, and that no name parameter exists. It does not discuss error cases or auth, but for a simple read/fetch operation this is adequate.

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?

The description is compact and every sentence earns its place: purpose, usage distinction, input provenance, output shape, and a critical constraint about name. It is front-loaded with the core purpose.

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 low-complexity tool with one required parameter and an output schema, the description covers the essential invocation context: when to use it, what to pass, what comes back, and how it differs from the relevant sibling. No significant information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only defines id as a string, with 0% description coverage. The description meaningfully compensates by explaining the id's provenance (from search, list_entities, or any reference) and explicitly stating that name is not a valid parameter, preventing a common misuse.

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 clearly identifies the tool as retrieving 'one entity's page as written' and explicitly contrasts it with get_entity for structured fields and references. This distinguishes it from siblings and states the resource being operated on.

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

Usage Guidelines5/5

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

It provides explicit routing guidance: use this tool to quote or display source, use get_entity for structured fields and references. It also tells the agent where ids come from (search, list_entities, or any reference) and warns that name input is not accepted.

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

All CompanyGraph tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?