Skip to main content
Glama

List the models saved on your account

list_graphs
Read-onlyIdempotent

Lists the graphs saved on your Neumann account, the most recently updated first. Use this when the user refers to a saved model that is not among the newest ones check_account_and_credits shows, or to page through all of them; it is how you find the id that get_graph, rank_inputs_by_impact, summarize_outcome_scenarios and delete_graph need. It does not list runs or results -- it lists the models themselves. It returns one entry per graph with its graph_id, name, when it was last updated and how many input and formula nodes it has, plus next_offset when there are more to page through. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. Cost: free -- it debits no credits and spends none of your free daily runs -- but it needs an account; an anonymous caller gets authentication_required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_graphs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many graphs to return, most recently updated first.
offsetNoHow many graphs to skip, for paging. Use the next_offset the previous call returned.

Output Schema

NameRequiredDescriptionDefault
graphsYesOne entry per saved graph, most recently updated first.
billingNoWho you are and what this call cost: principal, auth source, credits debited and balance, or the anonymous allowance left today.
next_offsetNoThe offset to pass next to get the following page, or null when this was the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds what they cannot: result ordering (most recently updated first), pagination via next_offset, the authentication requirement (Bearer key or token in the Authorization header, no api_key argument), the cost profile (free, consumes no credits or daily runs), and the exact failure mode (authentication_required for anonymous callers). That is substantial disclosure beyond structured data.

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?

Front-loaded with purpose and ordering, then usage, then return shape, then auth, then cost -- a sensible information hierarchy with no filler sentences. It is on the long side for a two-parameter lister, and the "No Neumann tool takes an api_key argument" aside is defensive padding, though it prevents a plausible misuse.

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 paginated read tool, the definition covers ordering, page continuation, returned identifiers, downstream consumers, auth mechanics and error behavior; an output schema already exists, so the return summary is a bonus rather than a gap. Nothing needed to invoke it correctly is missing.

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 coverage is 100% and both parameters are documented there, including limit's ordering and offset's use of next_offset. The description restates paging behavior without adding syntax or constraint detail beyond the schema, 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?

Specific verb and resource ("Lists the graphs saved on your Neumann account"), plus an explicit negative scope: "It does not list runs or results -- it lists the models themselves." That negative boundary is exactly what separates it from get_simulation_results and the run-oriented siblings.

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 names both when to use it (the user references a saved model not among the newest ones check_account_and_credits shows, or paging) and why (it yields the graph_id that get_graph, rank_inputs_by_impact, summarize_outcome_scenarios and delete_graph require). That is explicit routing to alternatives and prerequisites in one place.

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.

Resources