Gradient Dynamics: thermal and CFD simulation

List activity

list_activity

Read-onlyIdempotent

List engineering jobs, durable preparations and meaningful synchronous operations across your credentials. Filter a workflow or study to follow related work. Read-only; never retries compute. Each entry has a browser link. Unbound synchronous requests are visible only to their submitter.

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_activity"
  }
}

Input Schema

Name	Required	Default
`q`	No
`kind`	No
`view`	No
`after`	No
`limit`	No
`order`	No	newest
`state`	No
`user_id`	No
`category`	No
`study_id`	No
`project_id`	No
`entry_point`	No
`workflow_id`	No
`created_after`	No
`credential_id`	No
`created_before`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: 'never retries compute' clarifies that listing does not re-trigger underlying work, 'Each entry has a browser link' discloses the entry shape, and the submitter-visibility rule is a non-obvious access constraint.

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?

Sentences are short, front-loaded with the resource scope, and free of padding. The only weak line is the filter sentence, which is too implicit to earn its place as written.

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?

An output schema exists so return values need no explanation, but for a 16-parameter, all-optional filtering tool the description leaves the entire query surface undocumented including pagination and ordering semantics. Given the tool's complexity, this is a substantial shortfall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 16 parameters with 0% schema description coverage, so the description bears full responsibility and largely fails it. Only a vague hint toward workflow/study filtering appears; q, view, order, after/limit pagination, state, category, entry_point and the timestamp filters are left entirely undecoded.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-resource pair and scopes the resource set precisely: 'engineering jobs, durable preparations and meaningful synchronous operations across your credentials.' That is a genuine unified activity feed rather than a tautology, though it never names siblings like list_jobs or get_activity to make the boundary explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Filter a workflow or study to follow related work' implies a usage scenario, but there is no explicit when-to-use-this-versus-alternative guidance despite nearby siblings (list_jobs, get_activity) that overlap. The visibility caveat narrows expectations but is not routing guidance.

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

All Gradient Dynamics: thermal and CFD simulation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?