Skip to main content
Glama

Cortex

by io.cortex.mcp
OverviewDiscussionsAdmin

Get More Tools

get_more_tools
Read-only

Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesA description of your goal and what kind of tool would help accomplish it.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
mcp_sessionNoSession continuity and agent attribution state for this task, returned on completed responses that carry structured output. This server cannot link your calls between requests on its own, so session continuity travels here instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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: +[
+  "context",
+  "session_id"
+]
    • addedOutput schema / properties / mcp_session
      Added value: +{
+  "description": "Session continuity and agent attribution state for this task, returned on completed responses that carry structured output. This server cannot link your calls between requests on its own, so session continuity travels here instead.",
+  "properties": {
+    "session_id": {
+      "description": "Opaque correlation ID for this task, issued by this server. Use this as the session_id argument of every later call, and hand it to any subagents working the same task. Absent when status is unrecognized; no replacement is issued in that response — recovery is described under status.",
+      "type": "string"
+    },
+    "status": {
+      "description": "issued: first call of a task; the session_id above was just created. active: the session_id you sent was accepted; keep sending it. unrecognized: the value sent was not issued by this server — re-send the one issued earlier for this task; if none was issued yet, send start to be issued a new one.",
+      "enum": [
+        "issued",
+        "active",
+        "unrecognized"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  2. Changed6 schema fields changed
    • removedInput schema / properties / context / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / context / default
      Removed value: -""
    • addedInput schema / properties / context / description
      Added value: +"A description of your goal and what kind of tool would help accomplish it."
    • removedInput schema / properties / context / title
      Removed value: -"Context"
    • addedInput schema / properties / context / type
      Added value: +"string"
    • addedInput schema / required
      Added value: +[
+  "context"
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotation readOnlyHint=true already covers the safety profile. The description adds the purpose but not additional behavioral traits like return format or side effects. It doesn't contradict annotations, but it doesn't go beyond what the annotation already conveys. A 3 is appropriate given the annotation coverage.

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 a single, front-loaded sentence with no filler. It states the action and the condition for use in an efficient manner.

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 the main purpose and usage guidance. The parameters are fully documented in the schema, and an output schema exists. The only minor gap is that it doesn't hint at what kind of tools might be returned, but that is likely handled by the output schema. Overall, it's complete for a discovery tool.

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%, and both 'context' and 'session_id' have detailed descriptions. The tool description adds no extra meaning about the parameters, so the baseline of 3 applies.

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 states a specific action ('Check for additional tools') and the resource ('additional tools'). It also provides a clear condition for use, which distinguishes it from the many entity-specific get/list tools in the sibling list. No other sibling appears to be a meta-tool for discovery, so it stands apart.

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 explicitly says when to use it: 'whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.' This is clear context, though it doesn't mention alternatives or when not to use it. Since no other tool serves this discovery role, the guidance is sufficient.

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