補助・助成.jp

様式に記入する

fill_form

Destructive

欄ID→文字列を保存（置き換え）。clear は取消。Excel は sheet と番地、またはシート名!番地。PDF は p1.f12 の形。 from_profile=true はプロフィール候補の未記入欄をまとめて記入する。 rejected は未保存、その欄だけ修正する。warnings は保存済みなので見出しを確かめる。ラベル・記入例を残す場合はそれを含む全文を指定する。金額・数量は円単位等の半角数字。日付は利用者が伝えた値を書く（推奨日程への変更は利用者が認めてから）。 progress は入力候補の記入済み・残り。複数様式は fill_forms を使う。

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": {
      "form_id": "<form_id>",
      "values": "<values>"
    },
    "name": "fill_form"
  }
}

Input Schema

Name	Required	Description	Default
`clear`	No
`sheet`	No
`values`	Yes
`form_id`	Yes
`from_profile`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description is consistent with that by stating values are saved with replacement. It adds non-trivial behavioral context the annotations cannot convey: rejected entries are not persisted, warnings are already saved, and dates must reflect the user's stated value rather than recommendations without consent. It does not spell out irreversibility or permission requirements.

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 content is front-loaded with the core mapping behavior, which is good, but it is packed into a dense multi-line block of terse Japanese fragments with abrupt topic shifts between Excel, PDF, profile, and progress. Every line carries information, yet the structure makes scanning harder than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation tool with an output schema present, the description covers the main behavioral cases, entry formats, and the progress-returned semantics, so return values need not be re-explained. Only form_id and the security/permission context remain unaddressed.

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?

Schema description coverage is 0%, so the description carries the burden, and it does explain most parameters: values as field-ID-to-string mappings, clear as cancellation, sheet plus cell address format for Excel, and from_profile for bulk profile filling. form_id is only implicit. Solid compensation for an undocumented schema.

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 opening clause states a concrete verb and resource: saving a field-ID-to-string mapping into a form, with replacement semantics. It is clearly distinct from the sibling fill_forms, which it names for the multi-form case. The phrasing is terse and slightly cryptic, but an agent can tell what the tool does.

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

Usage Guidelines4/5

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

Explicit guidance is given for several paths: clear cancels entries, from_profile batch-fills empty profile fields, rejected values are unsaved so only that field is corrected, and warnings are already saved so headings should be checked. It also names the alternative fill_forms for multiple forms. Lacks explicit when-not-to-use framing, but the routing is clear.

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

All 補助・助成.jp 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?