Skip to main content
Glama

hash_fnv

Hash Sims 4 strings with FNV-1 to produce decimal, hex, and TGI-instance values for STBL keys and custom tuning resources.

Instructions

Hash a string with FNV-1 (Sims 4 resource/tuning convention).

Returns decimal, hex and TGI-instance representations.  STBL keys use
bits=32, high_bit=True; custom tuning instances use bits=64.

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": {
      "text": "<text>"
    },
    "name": "hash_fnv"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitsNo
textYes
high_bitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the return shape (decimal, hex, and TGI-instance representations), which an agent cannot otherwise infer since there is no output schema. It does not discuss determinism, error behavior, or what high_bit actually changes in the output, leaving a moderate gap for a zero-annotation tool.

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?

Three short sentences, front-loaded with the purpose and algorithm, followed by return values and then the parameter presets. Every sentence adds information, and nothing repeats the schema or the title.

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

Completeness4/5

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

For a three-parameter, annotation-free, no-output-schema tool, the definition covers purpose, algorithm choice, return representations, and the two presets that matter for the target domain. The remaining omissions (meaning of high_bit, role of bits=24, failure behavior) are real but minor for a deterministic pure function.

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?

Schema description coverage is 0%, so the description must compensate, and it does so partly: it pins bits=32/high_bit=True to STBL keys and bits=64 to tuning instances. However, it never explains what the high_bit flag means or what the bits=24 enum value is for, leaving roughly half the parameter space undefined.

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?

States a specific verb and resource (hash a string) plus the exact algorithm variant (FNV-1, explicitly not the more common FNV-1a) and the domain that motivates it (Sims 4 resource/tuning). No sibling tool in the list performs hashing, so the definition is unambiguous on its own terms.

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

Usage Guidelines4/5

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

Gives concrete when-to-use-which-settings guidance: STBL keys take bits=32 with high_bit=True, custom tuning instances take bits=64. That resolves the main choice an agent faces. It stops short of stating when not to use the tool or naming an alternative path, so it is not a full 5.

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