enquiry_fieldsEvery field of the Recruitment Agency Fees enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it discloses what the tool returns: key, label, type, required flag, help text, and allowed options. It implies a read-only introspection behavior, though it does not state response shape or absence of side effects explicitly.
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?
Two sentences pack an exact field inventory and a forward reference to submit_enquiry with no filler. The key information is front-loaded.
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?
For a zero-parameter tool with no output schema, the description sufficiently covers what the agent receives and how to use it. It does not explain the relationship to enquiry_describe, but that is not necessary for calling this tool correctly.
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?
The input schema has no parameters, so there are no parameter semantics to document. Baseline 4 applies because the description can add no parameter-level detail, and it instead clarifies how the returned keys connect to the submit_enquiry parameter keys.
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?
The description identifies the resource precisely (every field of the Recruitment Agency Fees enquiry) and enumerates the meta-attributes returned. It clearly signals that this is an introspection/form-definition tool, but it does not explicitly differentiate itself from the sibling enquiry_describe.
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?
It gives actionable guidance: pass answers to submit_enquiry keyed by field key, which tells an agent to fetch fields before submitting. It does not mention when to prefer this over enquiry_describe or offer explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: one explains the process, one provides the field schema, and one handles submission. There is no overlap or ambiguity between them.
Naming is mixed: two tools use the 'enquiry_' prefix (enquiry_describe, enquiry_fields) while submit_enquiry uses the suffix, and the patterns are noun_verb, noun_noun, and verb_noun. The shared 'enquiry' root keeps it readable, but the convention is not consistent.
Three tools is well-scoped for this narrow domain of submitting an enquiry. Each tool covers a necessary step, and none feel redundant or extraneous.
The workflow is fully covered: learn about the process, retrieve the required fields, and submit with consent and confirmation. There are no obvious missing operations for the stated purpose of handling Recruitment Agency Fees enquiries.