stocktoken_session_list
List agent sessions, optionally filtered by owner.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| owner | No |
AI Agent Tokenized Stock OS
by dev.aatos
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only states optional filter; no disclosure of return format, pagination, permissions, or side effects.
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?
Single sentence, no unnecessary words. Front-loaded with action and resource. Highly concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Simple tool but lacks context about session semantics, response structure, or business logic. No output schema and no annotations necessitate richer description for completeness.
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?
One parameter 'owner' with 0% schema description coverage. Description adds that it is an optional filter, which provides some meaning, but does not specify what owner represents (e.g., email, ID).
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 clearly states action (list) and resource (agent sessions), with optional filter by owner. Distinguishes from sibling tools like stocktoken_session_create, kill, update.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives (e.g., stocktoken_session_create or stocktoken_session_update). Does not mention when filtering is needed or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.9/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but some pairs (e.g., stocktoken_quote vs stocktoken_simulate, stocktoken_protocols vs stocktoken_find_pools) could cause confusion if descriptions are not read carefully.
Naming Consistency3/5
All tools share the 'stocktoken_' prefix, but the pattern is inconsistent: some use verb_noun (access_activate, execute_plan), others use single verb (get, list, simulate), and some use noun phrases (metrics, liquidity_matrix, morpho_deposit_plan).
Tool Count2/5
37 tools is high for an MCP server, covering access, subscriptions, sessions, tips, and trading. While many are needed for a full on-chain system, the count feels excessive and could be streamlined.
Completeness4/5
The server covers most major operations: listing, pricing, quoting, simulation, execution planning, liquidity, access control, and system management. Minor gaps exist (e.g., no broadcast tool, no explicit cancel/undo), but overall it's comprehensive.