Skip to main content
Glama

Submission status

getfund_submission_status
Read-only

A hosted run by runId, or the newest run of an application by applicationId: status (queued, starting, navigating, filling, reviewing, submitting, submitted, waiting_founder, failed, cancelled or expired), reason (waiting_founder: login, captcha, code, missing_answer, review or receipt; failed: blocked, payment, budget, browser_closed, navigator, form, caps, missing or no_form), handover (extension or new_run, after some failures), the run's times and watchUrl, its page on getfund. missing (waiting for missing_answer): the questions the run needs answers to, each with key, label, type and options. review (waiting for review): reviewSeq, fields (each field the form shows filled, with its label and value), empty (each field it shows empty, with the reason and whether it is required) and declarations (each with its id and the exact label the form gives it). proof (submitted): the receipt page's url and receiptText, or the founder's word (kind manual). A login, a CAPTCHA, a code and the receipt question are answered on the watch page. Needs applications:read.

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": "getfund_submission_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdNo
applicationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior5/5

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

It provides an exhaustive list of all possible statuses and detailed breakdowns of complex states like 'missing', 'review', and 'proof,' which is vital for agent decision-making.

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

Conciseness2/5

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

The description is a massive, monolithic block of text that is highly verbose. While comprehensive, its structure is extremely poor, making it difficult for an agent to parse quickly.

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?

Given the complexity of the submission lifecycle and the lack of an output schema, describing the exact structure of the various statuses is maximally complete for this definition.

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?

Since schema description coverage is 0%, the description does not add meaning to 'runId' or 'applicationId' beyond their basic context in the sentence. The schema carries the weight of defining these parameters.

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 clearly states the tool retrieves the status and various details for a submission run or application, giving concrete examples of the data returned.

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?

It implies usage for tracking submission progress, but does not explicitly state when this tool should be preferred over alternative status checks.

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