Skip to main content
Glama

Cortex

by io.cortex.mcp
OverviewDiscussionsAdmin

Searchcatalog

searchCatalog

Search the catalog for entities (services, domains, teams, resources), ranked by relevance. This is the primary way to find entities. Put search text in query (plain words work; AND/OR/NOT supported). Scope with types (e.g. service, domain, team); owners to get everything a team owns, including its sub-teams; domains to get everything within a domain, including its sub-domains; or catalog (a catalog slug). Returns a lean result per entity (cid, tag, type, name, description, owner emails, owning team tags, groups, status); groups are the free-form x-cortex-groups tags used to organize the catalog. Use getEntityDetails for the full record of a single entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo0-indexed page number.
queryNoRelevance search text. Plain words work; AND/OR/NOT supported.
typesNoRestrict to entity types, e.g. service, domain, team, resource.
ownersNoOwner team tags. Returns entities owned by these teams, including their sub-teams.
catalogNoCatalog slug. Scopes the search to that catalog's entities.
contextYes 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.
domainsNoDomain tags. Returns entities in these domains, including their sub-domains.
pageSizeNoResults per page, 1-100.
session_idYesSession 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.
includeArchivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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: -[
-  "context"
-]New value: +[
+  "session_id",
+  "context"
+]
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. Added
  7. Removed
  8. Added
  9. Removed
  10. Added
  11. Removed
  12. Added
  13. Removed
  14. Added
  15. Removed
  16. Added
  17. Removed
  18. Added
  19. Removed
  20. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses relevance ranking, a lean result shape, and explains the `groups` field semantics. It does not discuss pagination, includeArchived behavior, or empty-query behavior, though the schema provides defaults for some of these.

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?

Five dense sentences front-load purpose and move from query text to scoping to return contract. There is no filler, repetition, or irrelevant context.

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?

The description covers selection, invocation, scoping semantics, and return shape, which is especially important given there is no output schema. Minor omissions such as pagination behavior and includeArchived are mitigated by schema defaults and do not prevent correct invocation.

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?

Schema coverage is around 90%, but the description still adds value by explaining scoping effects and enumerating the returned lean fields (cid, tag, type, name, description, owner emails, owning team tags, groups, status). It also clarifies `groups` beyond the schema. Some parameter guidance, like AND/OR/NOT in query, repeats the schema, but the return-contract detail lifts it above baseline.

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?

Description uses a specific verb and resource ('Search the catalog for entities'), enumerates entity kinds (services, domains, teams, resources), and states relevance ranking. 'This is the primary way to find entities' positions it among siblings, and 'Use getEntityDetails for the full record' separates it from detail retrieval.

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?

The description clearly frames the tool as the primary entity-finding entry point and gives explicit scoping options. It names getEntityDetails as the alternative when a full record is needed, but it does not explicitly exclude other sibling search tools such as searchDeploys or say when listAllEntities would be preferable.

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

All Cortex toolsInspect
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