Skip to main content
Glama

Market Brew

Get license-definition form fields

get_license_definition_form_fields
Read-onlyIdempotent

Use this when the user asks to get license-definition form fields. Returns only data visible to the linked Market Brew account.

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": {
      "licenseDefinitionSummary": "<licenseDefinitionSummary>"
    },
    "name": "get_license_definition_form_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseDefinitionSummaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / licenseDefinitionSummary / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "exclusiveMinimum": 0,
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      },
      -      {
      -        "pattern": "^[1-9][0-9]{0,17}$",
      -        "type": "string"
      -      }
      -    ]
      -  },
      -  {
      -    "maxLength": 254,
      -    "minLength": 1,
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  {
      +    "maxLength": 254,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / licenseDefinitionSummary / anyOf
      Previous value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  {
      +    "maxLength": 254,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
  3. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description's one genuine addition is the data-scoping note that only data visible to the linked Market Brew account is returned, which is useful access context. It does not, however, say anything about the return shape or the form-field structure despite there being no output schema.

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?

It is short and front-loaded, but the first sentence is pure repetition of the name and earns no place. Only the second sentence carries information, so the signal-to-length ratio is weak even though the total is brief.

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?

With no output schema, the description must explain what 'form fields' actually are and how they come back, and it does not. For a tool whose sole required parameter is an ambiguous union type, leaving both the input meaning and the return shape unexplained leaves an agent under-equipped to invoke it correctly.

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?

Schema description coverage is 0% and the single required parameter, licenseDefinitionSummary, accepts an ambiguous union of a positive integer or a 1-254 character string. The description never mentions this parameter, so it cannot resolve whether the caller should pass a numeric ID or a name/slug. The self-describing parameter name is the only reason this is not a 1.

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

Purpose2/5

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

The sentence 'Use this when the user asks to get license-definition form fields' simply restates the tool name and title rather than describing what the tool actually does. It names the resource but offers no verb nuance or distinction from the sibling get_license_definition, which an agent would need to choose correctly.

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

Usage Guidelines2/5

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

The only usage guidance is circular: call it when the user asks for the thing the tool is named after. There is no mention of when to prefer this over get_license_definition, nor of prerequisites such as needing a valid license definition identifier.

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