Cortex

Getentitydetails

getEntityDetails

Retrieve comprehensive details about a specific entity including its metadata, ownership, hierarchies, and relationships. This is the primary method for getting complete information about services, teams, or domains.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your overall objective and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information.
`tagOrId`	Yes	Entity identifier - can be a tag or CID
`session_id`	Yes	Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.
`includeOwners`	No	Include ownership information, default is true
`hierarchyDepth`	No	Depth of the parent / children hierarchy nodes. Can be 'full' or a valid integer	full
`includeHierarchyFields`	No	List of sub fields to include for hierarchies. Only supports 'groups'

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 25, 2026

addedInput schema / properties / includeHierarchyFields / example
```
Added value: +"groups"
```

addedInput schema / properties / session_id

Added value: +{
+  "description": "Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.",
+  "pattern": "^(start|ses_[0-9A-Za-z]{27})$",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "tagOrId",
-  "context"
-]New value: +[
+  "tagOrId",
+  "session_id",
+  "context"
+]

First observedJan 31, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a broad set of information including metadata, ownership, hierarchies, and relationships, which sets expectations for output. However, it doesn't discuss potential performance implications of requesting deep hierarchies, or whether includeOwners defaulting to true might cause unexpected overhead. It's not misleading but leaves room for more behavioral context.

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 a single sentence that is clear and front-loaded with the main purpose. It efficiently conveys the scope of the data returned. It could arguably be more concise, but it is not verbose and every phrase contributes to the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 6 parameters, 3 required, and no output schema or annotations, the description should be more comprehensive. It covers what information is retrieved, but it doesn't explain how the parameters affect the response (e.g., includeOwners default, hierarchyDepth behavior). Some parameters like session_id are documented in the schema, but the overall orchestration context is missing. It's borderline adequate for a primary getter tool, but a bit more detail on parameter effects would be better.

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 description coverage is 100%, so the baseline is 3. The description does not add much parameter-specific guidance beyond the schema; it doesn't elaborate on what 'full' depth really means or how to use includeHierarchyFields effectively. The session_id parameter is well-explained in the schema, but the tool description does not supplement it. So, it's adequate but doesn't enhance clarity beyond the schema.

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 states a clear verb ('Retrieve comprehensive details') and resource ('specific entity'), and specifies the kinds of information included (metadata, ownership, hierarchies, relationships). It differentiates itself as the 'primary method' for complete entity details, though it doesn't explicitly distinguish from siblings like getDefinition or getEntityDescriptor, but the scope is clear.

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

Usage Guidelines3/5

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

The description implies that this is the go-to tool for complete entity details, but it doesn't explicitly state when to use it versus alternative tools or when not to use it. It mentions it's the 'primary method' but provides no exclusions or alternatives. The agent would need to infer that more specific tools like getTeamDetails or getScorecard exist for narrower use cases.

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

All Cortex tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?