Skip to main content
Glama
mintlineai

Mintline MCP Server

by mintlineai

create_tag

Create a new tag to categorize and organize your financial transactions and receipts in Mintline.

Instructions

Create tag. Create a new tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTag name
colorNoTag color (hex code, e.g., #10b981)

Implementation Reference

  • The handler for `create_tag` - formats the API response when a tag is created. This is part of the `formatResponse` function that maps API responses to human-readable text. The actual API execution is done by `executeAPICall` which dynamically resolves the endpoint from the OpenAPI spec.
    case "create_tag":
      return `Tag created: ${data.name} (${data.id})`;
  • src/index.js:333-334 (registration)
    Tool registration - the `CallToolRequestSchema` handler dispatches all tools dynamically. The `pathMap` is built from the OpenAPI spec (line 150-156) and `formatResponse` handles the `create_tag` case at line 285.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
  • Helper function that generates the tool definitions and path map from the OpenAPI spec. The `create_tag` tool is dynamically generated from the API spec - its operationId, parameters, and request body schema are parsed here.
    function generateToolsFromOpenAPI(spec) {
      const tools = [];
      const pathMap = {}; // operationId -> { method, path, parameters, requestBody }
    
      for (const [path, methods] of Object.entries(spec.paths)) {
        for (const [method, operation] of Object.entries(methods)) {
          const operationId = operation.operationId;
          if (!operationId) continue;
    
          // Build input schema from parameters and requestBody
          const properties = {};
          const required = [];
    
          // Add parameters (path + query)
          if (operation.parameters) {
            for (const param of operation.parameters) {
              properties[param.name] = {
                type: param.schema?.type || "string",
                description: param.description,
                enum: param.schema?.enum,
                default: param.schema?.default,
              };
              if (param.required) {
                required.push(param.name);
              }
            }
          }
    
          // Add request body properties
          if (operation.requestBody?.content?.["application/json"]?.schema?.properties) {
            const bodyProps = operation.requestBody.content["application/json"].schema.properties;
            const bodyRequired = operation.requestBody.content["application/json"].schema.required || [];
            for (const [name, prop] of Object.entries(bodyProps)) {
              properties[name] = {
                type: prop.type || "string",
                description: prop.description,
                enum: prop.enum,
                default: prop.default,
              };
            }
            required.push(...bodyRequired);
          }
    
          tools.push({
            name: operationId,
            description: `${operation.summary}. ${operation.description || ""}`.trim(),
            inputSchema: {
              type: "object",
              properties,
              required: required.length > 0 ? required : undefined,
            },
          });
    
          pathMap[operationId] = {
            method: method.toUpperCase(),
            path,
            parameters: operation.parameters || [],
            hasBody: !!operation.requestBody,
          };
        }
      }
    
      return { tools, pathMap };
    }
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., uniqueness constraints, authorization requirements, side effects). The simple phrase 'Create a new tag' conveys no behavioral context.

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?

Two sentences are used to convey the same tautological information. The description is not front-loaded with actionable details and contains redundancy without earning its length.

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

Completeness1/5

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

Given the tool has 2 parameters, no output schema, and no annotations, the description is woefully incomplete. It fails to explain what a tag represents, uniqueness rules, default color behavior, or any other crucial context for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 100% of parameters with clear descriptions (name required, color optional with hex example). The description adds no additional meaning beyond what the schema already provides, meeting the baseline of 3.

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

Purpose1/5

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

The description 'Create tag. Create a new tag.' is a tautology that merely restates the tool name without specifying what a tag is or its purpose in the system. It fails to distinguish from sibling tools like delete_tag or list_tags.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, edge cases, or comparison with sibling operations such as update or delete.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mintlineai/mintline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server