dms_to_decimal
Convert DMS (degrees, minutes, seconds) to decimal degrees.
This record as markdown: /tools/io-tinyfn-tinyfn/dms-to-decimal.md
What dms_to_decimal does on TinyFn
AI agents call dms_to_decimal to retrieve information from TinyFn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
degrees | integer | Yes | Degrees |
minutes | integer | Yes | Minutes |
seconds | number | Yes | Seconds |
direction | string | Yes | Direction: N, S, E, or W |
Parameters from the server's own tool schema.
Why dms_to_decimal is rated Low
This is a deterministic mathematical conversion tool that transforms coordinate format from DMS notation to decimal notation. It only reads input parameters and returns a computed result. No data is created, modified, deleted, or accessed externally. No code execution or financial operations occur. This aligns with the 'Read' category for retrieval and query operations with no side effects.
From the tool's definition Tool name 'dms_to_decimal' and description 'Convert DMS (degrees, minutes, seconds) to decimal degrees' indicate a pure conversion/calculation function that retrieves no external data, modifies nothing, and has no side effects.
Attacks that exploit this kind of access
The rule that runs dms_to_decimal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dms_to_decimal, this is the rule to start with:
dms_to_decimal is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every dms_to_decimal call is checked against it from then on.
Questions about dms_to_decimal
Convert DMS (degrees, minutes, seconds) to decimal degrees. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
dms_to_decimal accepts 4 parameters: degrees, minutes, seconds, direction. Required: degrees, minutes, seconds, direction. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for dms_to_decimal: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches TinyFn. Nothing to install.
dms_to_decimal is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dms_to_decimal rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for dms_to_decimal. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
dms_to_decimal is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue