Find a Nettskjema form using its short, URL-safe title identifier. Use when you have the titleShort from a public form URL and need the corresponding form.
Look up a form by its short title (the URL-safe identifier).
| Name | Required | Description | Default |
|---|---|---|---|
| title_short | Yes | The form's titleShort, as it appears in the form's public URL. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing behavioral beyond the lookup verb – no note on what happens on a miss (error vs empty), whether the lookup is exact-match or fuzzy, or what scope it searches.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence, front-loaded with the verb and resource, and the clarifying parenthetical is placed immediately after the qualifier. Nothing wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 not be described, and the tool is a simple one-parameter read. What is missing for full completeness is failure behavior and how the lookup relates to the id-based form-retrieval siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single parameter is fully documented in the schema. The description's parenthetical 'URL-safe identifier' merely restates the schema's 'titleShort, as it appears in the form's public URL', adding no new syntax or format detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (look up) and resource (form) with a scoping qualifier (by its short title). It implicitly separates itself from id-based siblings like get_form_info, but it never names an alternative, so sibling differentiation is left to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: an agent can infer it should call this when it has the URL-safe title rather than a numeric id. There is no explicit when-to-use/when-not guidance or pointer to get_form_info or list_my_forms as alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.