Skip to main content
Glama

Create a public link to a result

create_result_share_link
Idempotent

Creates a public web link to one of your results, so you can hand the numbers to someone who has no Neumann account. Use this when the user wants to send, publish or show a result to another person; to put the numbers in the conversation instead, call get_simulation_results. It works for any run you own: a run from run_monte_carlo_simulation, rank_inputs_by_impact or summarize_outcome_scenarios, and a run of a graph you saved. There is one share tool for every kind of run -- do not look for a separate one. Pass the run_id the run tool returned when the run was made, earlier in the conversation; no tool lists runs, and you do not need a graph_id. That holds for a run of a saved model too: when the user asks to share the run of a saved graph, call this tool directly with that run's run_id -- list_graphs and get_graph return graph_ids, not run_ids, so they are not a step here. Calling it again for the same run returns the same link rather than a second one. Anyone who has the link can open the result without signing in, so ask the user before you create one. delete_run deletes the stored result, which also stops its share link working. There is no way to turn off a link and keep the result. A run made without an account takes two calls, and the run_id is what carries it from one to the other. First call: the caller has no account, so call this tool with the run_id anyway; nothing is shared, and it returns a message asking the user to sign in with a free Kromatic account -- tell the user that. Second call: once the user has signed in, call this tool again with the SAME run_id. Only that second call shares the run and keeps it on the account; signing in alone shares nothing, and a different run_id, or a new run, does not carry the claim. Do it within 24 hours, because a run made without an account is deleted after that. When you tell the user what happens next, say both steps: sign in, then you will share it using the same run. It returns the share_url. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "create_result_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run to share, as returned by any run tool. For a run made without an account, sign in and then call again with this same run_id: signing in alone shares nothing.

Output Schema

NameRequiredDescriptionDefault
billingNoWho you are and what this call cost: principal, auth source, credits debited and balance, or the anonymous allowance left today.
share_urlYesA web address anyone can open to see this result, with no Neumann account and no credential. Asking again for the same run returns this same link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: confirms idempotency in concrete terms ('same run rather than a second one'), discloses the open-world consequence ('anyone who has the link can open the result without signing in'), states that delete_run kills the link and that there is no revoke-and-keep-result option, and documents the auth requirement plus the free cost profile. It even explains the two-call anonymous flow and the 24-hour expiry, none of which the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and alternative are front-loaded and every paragraph carries real information, but the prose is long and repetitive — 'signing in alone shares nothing' appears in both the description and the schema, and the no-account two-call flow is restated several times. A denser formulation could keep the same coverage in roughly half the length.

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 one-parameter tool with an output schema and rich annotations, the description covers everything an agent needs: auth, cost, idempotency, revocation behavior, expiry, and the multi-turn recovery path for anonymous runs. It also tells the agent what to say to the user, which closes the loop on the two-call flow.

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?

With one required parameter at 100% schema coverage, baseline would be 3, but the description genuinely adds semantics: the run_id must be the value returned by the run tool earlier in the conversation, no tool lists runs, no graph_id is needed, and the two-step anonymous flow requires reusing the SAME run_id. That is meaning the schema does not carry. It stops short of describing format/validation, which the schema already covers.

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?

States a specific verb and resource ('Creates a public web link to one of your results') and immediately bounds the scope ('someone who has no Neumann account'). It also names the sibling it is not (get_simulation_results) and clarifies that one share tool covers every run kind, so an agent cannot confuse it with 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?

Explicit when-to-use ('user wants to send, publish or show a result to another person'), explicit alternative with the condition that selects it ('to put the numbers in the conversation instead, call get_simulation_results'), and explicit when-not-a-step guidance ('list_graphs and get_graph return graph_ids, not run_ids, so they are not a step here'). The anonymous-user flow is spelled out step by step.

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