Skip to main content
Glama

get_attributions

Retrieve data source attributions and licences for all property data used by this server.

Instructions

Show data source attributions and licences for all data used by this server. Only call this tool when the user explicitly asks about data sources, credits, or attributions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_attributions' tool. Returns a static list of data source attributions (OpenStreetMap, URA, data.gov.sg) as a text response.
    async (_params, extra: ToolExtra) => {
      await logInfo(extra, "get_attributions: returning attribution list");
    
      return {
        content: [{
          type: "text" as const,
          text: `**Data Source Attributions**\n\nThis server uses the following data sources:\n\n${ATTRIBUTIONS.join("\n\n")}`,
        }],
      };
    },
  • The tool registration with name 'get_attributions', description, and an empty params schema (no input parameters required).
    "get_attributions",
    "Show data source attributions and licences for all data used by this server. Only call this tool when the user explicitly asks about data sources, credits, or attributions.",
    {},
  • Registration function that registers the 'get_attributions' tool on the MCP server via server.tool().
    export function registerAttributionTools(server: McpServer): void {
      server.tool(
        "get_attributions",
        "Show data source attributions and licences for all data used by this server. Only call this tool when the user explicitly asks about data sources, credits, or attributions.",
        {},
        async (_params, extra: ToolExtra) => {
          await logInfo(extra, "get_attributions: returning attribution list");
    
          return {
            content: [{
              type: "text" as const,
              text: `**Data Source Attributions**\n\nThis server uses the following data sources:\n\n${ATTRIBUTIONS.join("\n\n")}`,
            }],
          };
        },
      );
    }
  • src/index.ts:22-22 (registration)
    Main entry point: calls registerAttributionTools (which registers 'get_attributions') during server initialization.
    registerAttributionTools(server);
  • Helper function logInfo used by the handler to send an info-level log notification to the client.
    export async function logInfo(extra: ToolExtra, data: string): Promise<void> {
      await extra.sendNotification({
        method: "notifications/message" as const,
        params: { level: "info", logger: SERVER_NAME, data },
      });
    }
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It describes the tool as showing attributions and licences, implying a read-only operation. While it doesn't explicitly state it is non-destructive, the nature of the tool is clear and no side effects are expected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the first states the purpose, the second provides a usage guideline. No extraneous information, well-structured.

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

Completeness5/5

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

For a parameter-less, annotation-less tool with no output schema, the description is complete. It explains the functionality and when to use it, leaving no gaps.

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?

The input schema has zero parameters and 100% schema description coverage. The description does not need to add parameter details and does so appropriately.

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

Purpose5/5

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

The description clearly states 'Show data source attributions and licences for all data used by this server.' It uses a specific verb and resource, and is easily distinguishable from sibling tools like search or export.

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

Usage Guidelines5/5

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

The description explicitly says 'Only call this tool when the user explicitly asks about data sources, credits, or attributions.' This provides a clear when-to-use condition and implicitly tells the agent not to call it otherwise.

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/coolMukul/sg-property-mcp'

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